Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.6amended

claude-code-cache-fix vulnerable to local code execution via Python triple-quote injection in tools/quota-statusline.sh

CVE-2026-45136GHSA-g3xq-3gmv-qq8g

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (claude-code-cache-fix 3.5.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.6 · 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 · score source
EPSS
  • CVE-2026-45136: 0.19% estimated exploitation activity in the next 30 days; percentile 8.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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. Affected versions - v3.5.0 - v3.5.1 Patched versions - v3.5.2 Affected configurations Users 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. Attack chain Claude Code's statusline hook payload reflects user-controlled paths (cwd, workspace.currentdir, workspace.projectdir, transcriptpath). Apostrophes are legal in POSIX filesystem paths. 1. A hostile directory name containing '''+payload+''' lands on disk via any normal vector — git clone, archive extraction, npm package, downloaded zip, etc. 2. The victim has the…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-g3xq-3gmv-qq8g

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-g3xq-3gmv-qq8g

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-45136

Advisory: claude-code-cache-fix vulnerable to local code execution via Python triple-quote injection in tools/quota-statusline.sh
IDs: CVE-2026-45136, GHSA-g3xq-3gmv-qq8g
Record: https://patchnext.com/advisories/cve-2026-45136 (revision 3, source checked 26 Oct 2026, 12:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: claude-code-cache-fix 3.5.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm claude-code-cache-fix: affected >= 3.5.0, < 3.5.2; fixed in 3.5.2

## Suggested inspection (read-only)
- `npm ls claude-code-cache-fix --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on claude-code-cache-fix.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-g3xq-3gmv-qq8g (OSV record GHSA-g3xq-3gmv-qq8g lists affected ranges: npm claude-code-cache-fix >=3.5.0 <3.5.2 (fixed))
- Verified: https://github.com/advisories/GHSA-g3xq-3gmv-qq8g (GitHub-reviewed advisory GHSA-g3xq-3gmv-qq8g lists affected ranges: npm claude-code-cache-fix >=3.5.0 <3.5.2)

Commands are suggestions: review each one before running it.

Loading voting…