OS Command Injection in claude-code-cache-fix (CVE-2026-45136)
Summary
OS command injection in claude-code-cache-fix (CVE-2026-45136). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.5.2 or later.
Original description
The description as published by the source.
claude-code-cache-fix is a cache optimization proxy for Claude Code. From 3.5.0 to before 3.5.2, tools/quota-statusline.sh (introduced in v3.5.0) interpolates Claude Code's hook stdin payload directly into a Python triple-quoted string literal. A ''' byte sequence in any user-controlled field of the payload closes the literal early and lets following bytes execute as Python in the user's Claude Code process. This vulnerability is fixed in 3.5.2.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45136 has been found in claude-code-cache-fix.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade claude-code-cache-fix to 3.5.2 or later.
If unsure, ask your IT team or search "claude-code-cache-fix CVE-2026-45136" on the vendor's site.
CVE-2026-45136 (claude-code-cache-fix) — CWE-78 / CVSS v3 7.8
Attack vector: local / unauthenticated
Patched: 3.5.2 — 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.
OS command injection (CWE-78) exists in claude-code-cache-fix.
Check the vendor advisory for the affected versions of claude-code-cache-fix.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 3.5.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'claude-code-cache-fix' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'claude-code-cache-fix' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
claude-code-cache-fixを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade claude-code-cache-fix to 3.5.2ステージング環境で 3.5.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- report github.com
- web github.com
- web github.com