How severe is GHSA-ph6w-f82w-28w6?

No CVSS score has been assigned to GHSA-ph6w-f82w-28w6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-ph6w-f82w-28w6?

GHSA-ph6w-f82w-28w6 affects the following packages: @anthropic-ai/claude-code (npm). Ecosystems affected: npm.

How do I fix GHSA-ph6w-f82w-28w6?

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

How do I detect GHSA-ph6w-f82w-28w6 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-ph6w-f82w-28w6 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.

Is GHSA-ph6w-f82w-28w6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-ph6w-f82w-28w6 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.

When was GHSA-ph6w-f82w-28w6 published, and has it been updated?

GHSA-ph6w-f82w-28w6 was published on September 3, 2025 and was last updated on September 3, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Claude Code Vulnerable to Arbitrary Code Execution Due…

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.

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

@anthropic-ai/claude-codenpm

6.1Mdownloads / week

Description

When Claude Code was started in a new directory, it displayed a warning asking, "Do you trust the files in this folder?". This warning did not properly document that selecting "Yes, proceed" would allow Claude Code to execute files in the folder without additional confirmation. This may not have been clear to a user so we have updated the warning to clarify this functionality.

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

Thank you to https://hackerone.com/avivdon for reporting this issue!

Affected Packages

1 total 1 fixed

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

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 1.0.87 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ph6w-f82w-28w6 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.

Frequently Asked Questions

When Claude Code was started in a new directory, it displayed a warning asking, "Do you trust the files in this folder?". This warning did not properly document that selecting "Yes, proceed" would allow Claude Code to execute files in the folder without additional confirmation. This may not have been clear to a user so we have updated the warning to clarify this functionality. Users on standard Claude Code auto-update will have received this fix automatically. Users performing manual updates are advised to update to the latest version. Thank you to https://hackerone.com/avivdon for reportin

O3 Security · Impact-Aware SCA

Is GHSA-ph6w-f82w-28w6 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

Claude Code Vulnerable to Arbitrary Code Execution Due to Insufficient Startup WarningGHSA-ph6w-f82w-28w6