CVE-2026-45136: claude-code-cache-fix: Local code execution via Python triple-quote injection in tools/quota-statusline.sh
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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-45136 affects claude-code-cache-fix, a Claude Code cache optimization proxy. Vulnerable versions can turn crafted local hook input into Python code execution inside the user’s Claude Code process. The issue is serious for developer workstations using affected versions, but the provided sources do not show active exploitation.
Executive priority
Treat this as a high-priority developer tooling fix. The affected component can run code in a user’s Claude Code process, which may expose source code, credentials, or workstation access. Scope is likely narrow, so focus on fast inventory and upgrade rather than broad emergency response.
Technical view
Versions 3.5.0 through before 3.5.2 introduced tools/quota-statusline.sh, which placed Claude Code hook stdin directly inside a Python triple-quoted string. A controlled field containing a Python string delimiter could break parsing and allow unintended Python execution. The project reports the issue fixed in 3.5.2.
Likely exposure
Exposure is limited to environments running cnighswonger/claude-code-cache-fix versions 3.5.0, 3.5.1, or any build before 3.5.2 that uses the quota statusline hook path. It is most relevant to developer machines or automation contexts where Claude Code hooks process local input.
Exploitation context
The CVSS vector indicates local attack surface, low complexity, no privileges, and no user interaction. The source bundle marks KEV as false and provides no cited evidence of exploitation in the wild, so active exploitation should not be assumed.
Researcher notes
The strongest evidence is the GitHub advisory plus linked issue and pull request. The record identifies affected versions, vulnerable file, vulnerability pattern, CVSS 4.0 score, and fixed version. The bundle does not provide evidence of public exploitation or additional affected products.
Mitigation direction
Upgrade claude-code-cache-fix to version 3.5.2 or later.
Remove or disable affected quota-statusline hook usage until upgraded.
Check vendor advisory and release notes for any follow-up guidance.
Prioritize developer endpoints and CI hosts using Claude Code workflows.
Validation and detection
Inventory installed claude-code-cache-fix versions across developer and automation systems.
Confirm no host remains on versions 3.5.0 through before 3.5.2.
Review Claude Code hook configuration for tools/quota-statusline.sh usage.
Verify the fixed package is actually used by active workflows.
Check local logs for unexpected hook errors or Python execution symptoms.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.