dbcve.org
Zae LimiterApplication · Zeroae

CVE-2026-27695

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-25
Fix available
A fix is available. Upgrade to 0.10.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The zae-limiter library prior to version 0.10.1 uses a flawed DynamoDB partition key scheme where all rate limit buckets for a single entity share the same partition key (namespace/ENTITY#{id}). This causes all traffic for that entity to hit a single partition, exceeding DynamoDB's ~1,000 WCU/sec limit and causing throttling that affects both the high-traffic entity and other entities co-located in that partition.

MitigationUpgrade zae-limiter to version 0.10.1 or later, which implements a unique partition key per bucket to distribute load across DynamoDB partitions and prevent throttling.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Zae LimiterApplication
Affected:< 0.10.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify zae-limiter installation
    Check if zae-limiter is present in your environment by searching for it in your dependency files (requirements.txt, package.json, go.mod, pom.xml, Gemfile) or by running a package manager command like 'pip show zae-limiter', 'npm list zae-limiter', or 'go list -m all | grep zae-limiter'
    Affected if zae-limiter is found in your dependencies
  2. Verify the installed version
    Run 'pip show zae-limiter' or check your lock file to determine the exact version number installed
    Affected if The installed version is earlier than 0.10.1 (e.g., 0.10.0, 0.9.x, etc.)
  3. Confirm DynamoDB backend usage
    Examine your application configuration, environment variables, or connection settings to verify that DynamoDB is configured as the rate limiter backend. Look for AWS credentials, DynamoDB endpoint URLs, or table name configurations related to rate limiting
    Affected if DynamoDB is configured as the backend for rate limiting
  4. Inspect partition key configuration
    Review your rate limiter initialization code or configuration to examine the partition key pattern being used. If source code is accessible, look for how the key is constructed - specifically check if all buckets for an entity use a shared key in the format 'namespace/ENTITY#{id}' rather than a unique key per bucket
    Affected if The partition key scheme uses a single shared key (namespace/ENTITY#{id}) for all buckets of the same entity, causing all traffic to route to one DynamoDB partition

You are affected if zae-limiter version below 0.10.1 is installed and configured to use DynamoDB as the backend with the shared partition key scheme.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.10.1 or later
Fixed in 0.10.1
Interim mitigation

Upgrade zae-limiter to version 0.10.1 or later, which implements a unique partition key per bucket to distribute load across DynamoDB partitions and prevent throttling.

Recommended fix High confidence

0.10.1

  1. Identify the package manager used for zae-limiter in your project (npm, pip, composer, etc.)
  2. Locate zae-limiter in your dependency configuration file (package.json, requirements.txt, go.mod, etc.)
  3. Update the zae-limiter dependency to version 0.10.1
  4. Run dependency update/install command to fetch the fixed version
  5. Verify the installed version is 0.10.1 or higher
  6. Test your rate limiting functionality to ensure the upgrade does not break existing behavior

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zae Limiter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27695 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27695 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data