How severe is GHSA-q728-gf8j-w49r?

No CVSS score has been assigned to GHSA-q728-gf8j-w49r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q728-gf8j-w49r?

GHSA-q728-gf8j-w49r affects the following packages: @anthropic-ai/claude-code (npm). Ecosystems affected: npm.

How do I fix GHSA-q728-gf8j-w49r?

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

How do I detect GHSA-q728-gf8j-w49r in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @anthropic-ai/claude-code. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-q728-gf8j-w49r 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-q728-gf8j-w49r?

O3 pinpoints whether GHSA-q728-gf8j-w49r is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-q728-gf8j-w49r actively exploited in the wild?

No public exploit code has been indexed for GHSA-q728-gf8j-w49r 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-q728-gf8j-w49r?

GHSA-q728-gf8j-w49r has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 37th 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-q728-gf8j-w49r?

GHSA-q728-gf8j-w49r is classified as Path Traversal (CWE-22), Cross-site Scripting (XSS) (CWE-79). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-q728-gf8j-w49r published, and has it been updated?

GHSA-q728-gf8j-w49r was published on February 3, 2026 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-q728-gf8j-w49r: @anthropic-ai/claude-code

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk37th percentile+0.44%

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.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

@anthropic-ai/claude-codenpm

10.1Mdownloads / week

Description

Due to a Bash command validation flaw in parsing ZSH clobber syntax, it was possible to bypass directory restrictions and write files outside the current working directory without user permission prompts. Exploiting this required the user to use ZSH and the ability to add untrusted content into a Claude Code context window.

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 https://hackerone.com/alexbernier for reporting this issue!

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@anthropic-ai/claude-code`	all versions	2.0.74

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @anthropic-ai/claude-code to 2.0.74 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q728-gf8j-w49r 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 pinpoints whether GHSA-q728-gf8j-w49r is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

Frequently Asked Questions

Due to a Bash command validation flaw in parsing ZSH clobber syntax, it was possible to bypass directory restrictions and write files outside the current working directory without user permission prompts. Exploiting this required the user to use ZSH and the ability to add untrusted content into a Claude Code context window. 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 https://hackerone.com/alexbernier for reporting this issue!

O3 Security · Impact-Aware SCA

Is GHSA-q728-gf8j-w49r in your dependencies?

O3 detects GHSA-q728-gf8j-w49r across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-q728-gf8j-w49r