← Back
CVE-2026-27695
Vulnerability in zae-limiter (CVE-2026-27695)
Summary
vulnerability in zae-limiter (CVE-2026-27695). Risk of unauthorized operations or information disclosure. Exploitable via ``TransactWriteItems``. Mitigation: upgrade to `0.10.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-27695** has been found in zae-limiter.
Attackers can target a specific entry point like ``TransactWriteItems`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade zae-limiter to **0.10.1** or later.
If unsure, ask your IT team or search "zae-limiter CVE-2026-27695" on the vendor's site.
CVE-2026-27695 (zae-limiter) — CWE-770 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `TransactWriteItems` / `UpdateItem` / `ProvisionedThroughputExceededException` / `RateLimiterUnavailable`
Patched: `0.10.1` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-770) exists in zae-limiter. Attackers reach the vulnerable code path via ``TransactWriteItems`` without authentication.
📍 Affected scope
zae-limiter — . Attack surface: `TransactWriteItems` / `UpdateItem` / `ProvisionedThroughputExceededException` / `RateLimiterUnavailable`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.10.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'zae-limiter' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'zae-limiter' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `zae-limiter` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade zae-limiter to 0.10.1ステージング環境で 0.10.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
zae-limiter
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.10.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-27695
- advisory https://github.com/advisories/GHSA-76rv-2r9v-c5m6
- package https://github.com/zeroae/zae-limiter
- package https://pypi.org/project/zae-limiter
- web https://github.com/zeroae/zae-limiter/security/advisories/GHSA-76rv-2r9v-c5m6
- web https://github.com/zeroae/zae-limiter/commit/481ce44d818d66e31d8837bc48519660ce4c267f
- web https://github.com/zeroae/zae-limiter/releases/tag/v0.10.1