CVE-2026-45136: Claude code cache fix Claude-code-cache-fix Vulnerable To Local Code Vulnerability
HIGHCVE-2026-45136 is a HIGH (CVSS 7.8) claude-code-cache-fix vulnerable to local code vulnerability (CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')) affecting Claude code cache fix libraries in the npm ecosystem. The issue involves claude-code-cache-fix vulnerable to local code execution via python triple-quote injection in tools/quota-statusline.sh. Remediation is available by upgrading affected packages to version 3.5.2.
CVE-2026-45136 at a Glance
Security Impact
CVSS: 7.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).
How to Fix CVE-2026-45136
To remediate this vulnerability, upgrade all affected Claude code cache fix dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install claude-code-cache-fix@3.5.2
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls claude-code-cache-fix
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-45136, inspect your project dependencies using npm:
npm ls claude-code-cache-fix
Analyze the terminal output to locate any version of Claude code cache fix in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.5.2), your application is affected.
Note: The npm ls claude-code-cache-fix command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'), where the product constructs all or part of an os command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended os command when it is sent to a downstream component. In Claude code cache fix, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-45136 Affected Claude code cache fix Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
claude-code-cache-fix
|
npm |
≥ 3.5.0
< 3.5.2
|
3.5.2
|
References
Frequently Asked Questions
What is CVE-2026-45136?
Which Claude code cache fix versions are affected?
What version fixes CVE-2026-45136?
Is claude-code-cache-fix affected?
What is the CVSS score of CVE-2026-45136?
What CWE is associated with CVE-2026-45136?
How can I check npm dependencies for CVE-2026-45136?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-g3xq-3gmv-qq8g",
"modified" : "2026-06-08T23:54:32Z",
"published" : "2026-05-13T15:31:41Z",
"aliases" : [ "CVE-2026-45136" ],
"summary" : "claude-code-cache-fix vulnerable to local code execution via Python triple-quote injection in tools/quota-statusline.sh",
"details" : "## Summary\n\n`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.\n\n## Affected versions\n\n- v3.5.0\n- v3.5.1\n\n## Patched versions\n\n- v3.5.2\n\n## Affected configurations\n\nUsers who wired `tools/quota-statusline.sh` into Claude Code's `statusLine` configuration. The v3.5.0 README explicitly recommends this setup, so most users on v3.5.0/v3.5.1 with the recommended setup are affected.\n\n## Attack chain\n\nClaude Code's statusline hook payload reflects user-controlled paths (`cwd`, `workspace.current_dir`, `workspace.project_dir`, `transcript_path`). Apostrophes are legal in POSIX filesystem paths.\n\n1. A hostile directory name containing `'''+payload+'''` lands on disk via any normal vector — `git clone`, archive extraction, npm package, downloaded zip, etc.\n2. The victim has the recommended `tools/quota-statusline.sh` wired into their CC `statusLine` config.\n3. The victim `cd`s anywhere a hostile path is reachable.\n4. CC fires the statusline hook on every redraw. The Python literal closes early. The injected bytes execute as Python in the user's process.\n\n## Severity\n\nLocal code execution at user privilege. Persistent re-fire on every statusline redraw. No user interaction beyond `cd`-ing into the hostile path. The user's shell, CC session, files, SSH keys, and any locally-accessible credentials are reachable from the executed code.\n\n## Vulnerable pattern\n\n```sh\ninput=$(cat)\nresult=$(python3 -c \"\n stdin_data = json.loads('''$input''') if '''$input''' else {}\n\")\n```\n\n## Fix\n\nCapture stdin in bash, export to env, and pipe the Python source through a single-quoted heredoc (`<<'PYEOF'`). Single-quoting disables ALL bash interpolation inside the body. Python reads the JSON via `os.environ.get('CC_INPUT')`, where the bytes are inert at every layer.\n\n```sh\nCC_INPUT=$(cat)\nexport CC_INPUT\n\npython3 <<'PYEOF' 2>/dev/null\nimport os, json\ntry:\n cc_input = json.loads(os.environ.get('CC_INPUT') or '{}')\nexcept Exception:\n cc_input = {}\n# ...\nPYEOF\n```\n\n## Workarounds\n\nUntil upgrading to v3.5.2:\n\n- Disable the statusline by removing the `statusLine` entry from `~/.claude/settings.json`, or\n- Replace `tools/quota-statusline.sh` with a script that does NOT pass stdin through `python3 -c \"...\"` (a heredoc + env var rewrite is safe)\n\n## Credit\n\nReported by Jakob Linke (@schuay) via GitHub issue [#108](https://github.com/cnighswonger/claude-code-cache-fix/issues/108).\n\n## Timeline\n\n- 2026-05-07 — reported (#108)\n- 2026-05-07 — confirmed, fix implemented (#110)\n- 2026-05-07 — v3.5.2 published",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
}, {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "claude-code-cache-fix"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "3.5.0"
}, {
"fixed" : "3.5.2"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/cnighswonger/claude-code-cache-fix/security/advisories/GHSA-g3xq-3gmv-qq8g"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-45136"
}, {
"type" : "WEB",
"url" : "https://github.com/cnighswonger/claude-code-cache-fix/issues/108"
}, {
"type" : "WEB",
"url" : "https://github.com/cnighswonger/claude-code-cache-fix/pull/110"
}, {
"type" : "WEB",
"url" : "https://github.com/cnighswonger/claude-code-cache-fix/commit/613e4df30547f3e6baf32d161eddc828f171da17"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/cnighswonger/claude-code-cache-fix"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-78", "CWE-94" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-05-13T15:31:41Z",
"nvd_published_at" : "2026-05-27T21:16:18Z"
}
}