CVE-2026-27695: zae-limiter Denial of Service Vulnerability

MODERATE
Advisory Identifier: GHSA-76rv-2r9v-c5m6
CVSS 4.3
CWE-770
Published
Advisory Summary

CVE-2026-27695 is a MODERATE (CVSS 4.3) denial of service vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting zae-limiter libraries in the PyPI ecosystem. The issue involves dynamodb hot partition throttling enables per-entity denial of service. Remediation is available by upgrading affected packages to version 0.10.1.

CVE-2026-27695 at a Glance

CVE Identifier CVE-2026-27695
GHSA Identifier GHSA-76rv-2r9v-c5m6
Severity MODERATE
CVSS v3.1 Base Score 4.3
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
Affected Product zae-limiter
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 4.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability Low (A:L)

How to Fix CVE-2026-27695

To remediate this vulnerability, upgrade all affected zae-limiter dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

zae-limiter fixed: 0.10.1
pip install zae-limiter>=0.10.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show zae-limiter

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-27695, inspect your installed packages using pip:

pip show zae-limiter

Analyze the terminal output to locate any version of zae-limiter in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.10.1), your application is affected.

Note: The pip show zae-limiter command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In zae-limiter, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary 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. ## Details Each `acquire()` call performs a `TransactWriteItems` (or `UpdateItem` in speculative mode) against items sharing the same partition key. For cascade entities, this doubles to 2-4 writes per request (child + parent). At sustained rates above ~500 req/sec for a single entity, DynamoDB's adaptive capacity may not redistribute fast enough, causing `ProvisionedThroughputExceededException`. The library has no built-in mitigation: - No partition key sharding/salting - No write coalescing or batching - No client-side admission control before hitting DynamoDB - `RateLimiterUnavailable` is raised but the caller has already been delayed ## Impact - **Availability**: High-traffic entities experience elevated latency and rejected requests beyond what their rate limits specify - **Fairness**: Other entities sharing the same DynamoDB partition may experience collateral throttling - **Multi-tenant risk**: In a shared LLM proxy scenario, one tenant's burst traffic could degrade service for others ## Reproduction 1. Create an entity with high rate limits (e.g., 100,000 rpm) 2. Send sustained traffic at 1,000+ req/sec to a single entity 3. Observe DynamoDB `ThrottledRequests` CloudWatch metric increasing 4. Observe `acquire()` latency spikes and `RateLimiterUnavailable` exceptions ## Remediation Design: Pre-Shard Buckets - Move buckets to `PK={ns}/BUCKET#{entity}#{resource}#{shard}, SK=#STATE` — one partition per (entity, resource, shard) - Auto-inject `wcu:1000` reserved limit on every bucket — tracks DynamoDB partition write pressure in-band (name may change during implementation) - Shard doubling (1→2→4→8) triggered by client on `wcu` exhaustion or proactively by aggregator - Shard 0 at suffix `#0` is source of truth for `shard_count`. Aggregator propagates to other shards - Original limits stored on bucket, effective limits derived: `original / shard_count`. Infrastructure limits (`wcu`) not divided - Shard selection: random/round-robin. On application limit exhaustion, retry on another shard (max 2 retries) - Lazy shard creation on first access - Bucket discovery via GSI3 (KEYS_ONLY) + BatchGetItem. GSI2 for resource aggregation unchanged - Cascade: parent unaware, protected by own `wcu` - Aggregator: parse new PK format, key by shard_id, effective limits for refill, filter `wcu` from snapshots - Clean break migration: schema version bump, old buckets ignored, new buckets created on first access - **$0.625/M preserved on hot path**

CVE-2026-27695 Affected zae-limiter Versions

1 component(s)
Fixed Versions:
0.10.1
Product / Package Ecosystem Affected Versions Fixed Version
zae-limiter
PyPI
< 0.10.1
0.10.1

References

Frequently Asked Questions

What is CVE-2026-27695?
CVE-2026-27695 is a security vulnerability in zae-limiter involving DynamoDB hot partition throttling enables per-entity Denial of Service under CWE-770: Allocation of Resources Without Limits or Throttling.
Which zae-limiter versions are affected?
Affected versions include releases prior to 0.10.1 across affected packages: zae-limiter.
What version fixes CVE-2026-27695?
Upgrading to 0.10.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is zae-limiter affected?
Yes, zae-limiter is affected in releases prior to 0.10.1. Upgrade your dependency to 0.10.1 or later.
What is the CVSS score of CVE-2026-27695?
CVE-2026-27695 has a CVSS v3.1 base score of 4.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L.
What CWE is associated with CVE-2026-27695?
CVE-2026-27695 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.).
How can I check PyPI dependencies for CVE-2026-27695?
Run the dependency tree command: 'pip show zae-limiter'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-76rv-2r9v-c5m6",
  "modified" : "2026-02-25T22:31:10Z",
  "published" : "2026-02-25T22:31:10Z",
  "aliases" : [ "CVE-2026-27695" ],
  "summary" : "zae-limiter: DynamoDB hot partition throttling enables per-entity Denial of Service",
  "details" : "## Summary\n\nAll 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.\n\n## Details\n\nEach `acquire()` call performs a `TransactWriteItems` (or `UpdateItem` in speculative mode) against items sharing the same partition key. For cascade entities, this doubles to 2-4 writes per request (child + parent). At sustained rates above ~500 req/sec for a single entity, DynamoDB's adaptive capacity may not redistribute fast enough, causing `ProvisionedThroughputExceededException`.\n\nThe library has no built-in mitigation:\n- No partition key sharding/salting\n- No write coalescing or batching\n- No client-side admission control before hitting DynamoDB\n- `RateLimiterUnavailable` is raised but the caller has already been delayed\n\n## Impact\n\n- **Availability**: High-traffic entities experience elevated latency and rejected requests beyond what their rate limits specify\n- **Fairness**: Other entities sharing the same DynamoDB partition may experience collateral throttling\n- **Multi-tenant risk**: In a shared LLM proxy scenario, one tenant's burst traffic could degrade service for others\n\n## Reproduction\n\n1. Create an entity with high rate limits (e.g., 100,000 rpm)\n2. Send sustained traffic at 1,000+ req/sec to a single entity\n3. Observe DynamoDB `ThrottledRequests` CloudWatch metric increasing\n4. Observe `acquire()` latency spikes and `RateLimiterUnavailable` exceptions\n\n## Remediation Design: Pre-Shard Buckets\n\n- Move buckets to `PK={ns}/BUCKET#{entity}#{resource}#{shard}, SK=#STATE` — one partition per (entity, resource, shard)\n- Auto-inject `wcu:1000` reserved limit on every bucket — tracks DynamoDB partition write pressure in-band (name may change during implementation)\n- Shard doubling (1→2→4→8) triggered by client on `wcu` exhaustion or proactively by aggregator\n- Shard 0 at suffix `#0` is source of truth for `shard_count`. Aggregator propagates to other shards\n- Original limits stored on bucket, effective limits derived: `original / shard_count`. Infrastructure limits (`wcu`) not divided\n- Shard selection: random/round-robin. On application limit exhaustion, retry on another shard (max 2 retries)\n- Lazy shard creation on first access\n- Bucket discovery via GSI3 (KEYS_ONLY) + BatchGetItem. GSI2 for resource aggregation unchanged\n- Cascade: parent unaware, protected by own `wcu`\n- Aggregator: parse new PK format, key by shard_id, effective limits for refill, filter `wcu` from snapshots\n- Clean break migration: schema version bump, old buckets ignored, new buckets created on first access\n- **$0.625/M preserved on hot path**",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "zae-limiter"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.10.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.10.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/zeroae/zae-limiter/security/advisories/GHSA-76rv-2r9v-c5m6"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-27695"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zeroae/zae-limiter/commit/481ce44d818d66e31d8837bc48519660ce4c267f"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/zeroae/zae-limiter"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zeroae/zae-limiter/releases/tag/v0.10.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-770" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-25T22:31:10Z",
    "nvd_published_at" : "2026-02-25T15:20:52Z"
  }
}