Skip to content

← Public intelligence

npm package

claude-code-cache-fix

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.6npmAmendedPublished

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

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

    Affected
    • npm claude-code-cache-fix >= 3.5.0, < 3.5.2
    Fixed in
    3.5.2· Vendor fix available
    Issue
    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…

    Recommended action: Upgrade to 3.5.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →