How severe is CVE-2026-45136?

No CVSS score has been assigned to CVE-2026-45136 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-45136?

CVE-2026-45136 affects the following packages: claude-code-cache-fix (npm). Ecosystems affected: npm.

How do I fix CVE-2026-45136?

Update claude-code-cache-fix to 3.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-45136 is resolved across your whole dependency graph.

How do I detect CVE-2026-45136 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for claude-code-cache-fix. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2026-45136 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2026-45136?

O3 pinpoints whether CVE-2026-45136 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2026-45136 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-45136 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was CVE-2026-45136 published, and has it been updated?

CVE-2026-45136 was published on May 27, 2026 and was last updated on July 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-45136

Fix: cnighswonger/claude-code-cache-fix#110

CVE-2026-45136 is a security vulnerability in claude-code-cache-fix. O3 Security confirms whether CVE-2026-45136 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

claude-code-cache-fix: Local code execution via Python triple-quote injection in tools/quota-statusline.sh

Also known asGHSA-g3xq-3gmv-qq8g

Published

May 27, 2026

Updated

Jul 15, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 15, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦claude-code-cache-fix

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`claude-code-cache-fix`	≥ 3.5.0&&< 3.5.2	3.5.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for claude-code-cache-fix. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update claude-code-cache-fix to 3.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-45136 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-45136 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2026-45136. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-45136 in your dependencies?

O3 detects CVE-2026-45136 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works