CVE-2026-27695: zae-limiter is a rate limiting library using the token bucket algorithm

Q: How do I fix CVE-2026-27695?

zae-limiter: upgrade to 0.10.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-27695 being exploited?

CVE-2026-27695 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-27695 affect?

CVE-2026-27695 affects zae-limiter. Severity is medium (CVSS 4.3). zae-limiter is a rate limiting library using the token bucket algorithm. Prior to version 0.10.1, all rate limit buckets for a single entity share the same DynamoDB partition key (`namespace/ENTITY#{id}`). A high-traffic entity can exceed D

Q: How urgent is CVE-2026-27695?

Priority 20/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2026-27695 is a medium-severity flaw (CVSS 4.3) affecting zae-limiter. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

zae-limiter is a rate limiting library using the token bucket algorithm. Prior to version 0.10.1, all rate limit buckets for a single entity share the same DynamoDB partition key (`namespace/ENTITY#{id}`). A high-traffic entity can exceed DynamoDB's per-partition throughput limits (~1,000 WCU/sec), causing throttling that degrades service for that entity — and potentially co-located entities in the same partition. Version 0.10.1 fixes the issue.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 81%)
CISA exploited list	No
Weakness	CWE-770
Published	2026-02-25
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: zeroae

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-02-25 15:20 UTCPublished CVE record published
2026-06-17 10:27 UTCUpdated Record last modified

zeroae zae-limiter UPGRADE

Affected: < 0.10.1

Fixed in: 0.10.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy zae-limiter || rpm -q zae-limiter || zae-limiter --version

2. UPGRADE to 0.10.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade zae-limiter

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade zae-limiter

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-27695?

zae-limiter: upgrade to 0.10.1. Exact commands for each OS are on this page.

Is CVE-2026-27695 being exploited?

CVE-2026-27695 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-27695 affect?

CVE-2026-27695 affects zae-limiter. Severity is medium (CVSS 4.3). zae-limiter is a rate limiting library using the token bucket algorithm. Prior to version 0.10.1, all rate limit buckets for a single entity share the same DynamoDB partition key (`namespace/ENTITY#{id}`). A high-traffic entity can exceed D

How urgent is CVE-2026-27695?

Priority 20/100. No elevated risk signals yet.

References

← Back to latest CVEs