← Back
CVE-2026-45136
OS Command Injection in claude-code-cache-fix (CVE-2026-45136)
Summary
OS command injection in claude-code-cache-fix (CVE-2026-45136). Risk of unauthorized operations or information disclosure. Exploitable via ``statusLine``. Mitigation: upgrade to `3.5.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45136** has been found in claude-code-cache-fix.
Attackers can target a specific entry point like ``statusLine`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/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 /
Attack surface: `statusLine` / `cwd` / `workspace.current_dir` / `workspace.project_dir`
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.
❓ What is the problem
**OS command injection** (CWE-78) exists in claude-code-cache-fix. Attackers reach the vulnerable code path via ``statusLine`` without authentication.
📍 Affected scope
claude-code-cache-fix — . Attack surface: `statusLine` / `cwd` / `workspace.current_dir` / `workspace.project_dir`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.5.2**.
🛡️ 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 'claude-code-cache-fix' .` 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 'claude-code-cache-fix' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `claude-code-cache-fix` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade claude-code-cache-fix to 3.5.2ステージング環境で 3.5.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
claude-code-cache-fix
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.5.2"}]}]
References
- web https://github.com/cnighswonger/claude-code-cache-fix/security/advisories/GHSA-g3xq-3gmv-qq8g
- web https://github.com/cnighswonger/claude-code-cache-fix/issues/108
- web https://github.com/cnighswonger/claude-code-cache-fix/pull/110
- web https://github.com/cnighswonger/claude-code-cache-fix/commit/613e4df30547f3e6baf32d161eddc828f171da17
- web https://github.com/advisories/GHSA-g3xq-3gmv-qq8g