How severe is GHSA-q5hj-mxqh-vv77?

No CVSS score has been assigned to GHSA-q5hj-mxqh-vv77 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q5hj-mxqh-vv77?

GHSA-q5hj-mxqh-vv77 affects the following packages: @anthropic-ai/claude-code (npm). Ecosystems affected: npm.

How do I fix GHSA-q5hj-mxqh-vv77?

Update @anthropic-ai/claude-code to 2.1.84 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q5hj-mxqh-vv77 is resolved across your whole dependency graph.

How do I detect GHSA-q5hj-mxqh-vv77 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @anthropic-ai/claude-code, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-q5hj-mxqh-vv77 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 GHSA-q5hj-mxqh-vv77?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-q5hj-mxqh-vv77 can be triaged on real exposure rather than presence alone.

Is GHSA-q5hj-mxqh-vv77 actively exploited in the wild?

No public exploit code has been indexed for GHSA-q5hj-mxqh-vv77 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.

What is the EPSS score for GHSA-q5hj-mxqh-vv77?

GHSA-q5hj-mxqh-vv77 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 25th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-q5hj-mxqh-vv77?

GHSA-q5hj-mxqh-vv77 is classified as Improper Input Validation (CWE-20), CWE-77 (CWE-77). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-q5hj-mxqh-vv77 published, and has it been updated?

GHSA-q5hj-mxqh-vv77 was published on April 24, 2026 and was last updated on May 8, 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

GHSA-q5hj-mxqh-vv77 — @anthropic-ai/claude-code

GHSA-q5hj-mxqh-vv77 is a Improper Input Validation vulnerability in @anthropic-ai/claude-code. A fix is available for @anthropic-ai/claude-code — see the affected versions and patch details below.

Claude Code: Trust Dialog Bypass via Git Worktree Spoofing Allows Arbitrary Code Execution

Also known asCVE-2026-40068

Published

Apr 24, 2026

Updated

May 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-q5hj-mxqh-vv77.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs25th percentile — riskier than 25% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

273other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@anthropic-ai/claude-codenpm

8.7Mdownloads / week

Description

Claude Code used the git worktree commondir file when determining folder trust but did not validate its contents. By crafting a repository with a commondir file pointing to a path the victim had previously trusted, an attacker could bypass the trust dialog and immediately execute malicious hooks defined in .claude/settings.json. Exploiting this required the victim to clone a malicious repository and run Claude Code within it, and for the attacker to know or guess a path the victim had already trusted.

Users on standard Claude Code auto-update have received this fix already. Users performing manual updates are advised to update to the latest version.

Claude Code thanks hackerone.com/masato_anzai for reporting this issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@anthropic-ai/claude-code`	≥ 2.1.63&&< 2.1.84	2.1.84`npm install @anthropic-ai/claude-code@2.1.84`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @anthropic-ai/claude-code, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @anthropic-ai/claude-code to 2.1.84 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q5hj-mxqh-vv77 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-q5hj-mxqh-vv77 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-q5hj-mxqh-vv77. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Claude Code used the git worktree `commondir` file when determining folder trust but did not validate its contents. By crafting a repository with a `commondir` file pointing to a path the victim had previously trusted, an attacker could bypass the trust dialog and immediately execute malicious hooks defined in `.claude/settings.json`. Exploiting this required the victim to clone a malicious repository and run Claude Code within it, and for the attacker to know or guess a path the victim had already trusted. Users on standard Claude Code auto-update have received this fix already. Users perfor

O3 Security · Impact-Aware SCA

Is GHSA-q5hj-mxqh-vv77 in your dependencies?

O3 Security finds GHSA-q5hj-mxqh-vv77 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works