How severe is GHSA-p7fg-763f-g4gf?

No CVSS score has been assigned to GHSA-p7fg-763f-g4gf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p7fg-763f-g4gf?

GHSA-p7fg-763f-g4gf affects the following packages: @anthropic-ai/sdk (npm). Ecosystems affected: npm.

How do I fix GHSA-p7fg-763f-g4gf?

Update @anthropic-ai/sdk to 0.91.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p7fg-763f-g4gf is resolved across your whole dependency graph.

How do I detect GHSA-p7fg-763f-g4gf in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @anthropic-ai/sdk. 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-p7fg-763f-g4gf 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-p7fg-763f-g4gf?

O3 pinpoints whether GHSA-p7fg-763f-g4gf 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-p7fg-763f-g4gf actively exploited in the wild?

No public exploit code has been indexed for GHSA-p7fg-763f-g4gf 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-p7fg-763f-g4gf published, and has it been updated?

GHSA-p7fg-763f-g4gf was published on April 29, 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

GHSA-p7fg-763f-g4gf

GHSA-p7fg-763f-g4gf is a security vulnerability in @anthropic-ai/sdk. O3 Security confirms whether GHSA-p7fg-763f-g4gf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Claude SDK for TypeScript has Insecure Default File Permissions in Local Filesystem Memory Tool

Also known asCVE-2026-41686

Published

Apr 29, 2026

Updated

May 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

📦@anthropic-ai/sdk

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

The BetaLocalFilesystemMemoryTool in the Anthropic TypeScript SDK created memory files and directories using the Node.js default modes (0o666 for files, 0o777 for directories), leaving them world-readable on systems with a standard umask and world-writable in environments with a permissive umask such as many Docker base images. A local attacker on a shared host could read persisted agent state, and in containerized deployments could modify memory files to influence subsequent model behavior.

Users on the affected versions are advised to update to the latest version.

Claude SDK thanks lucasfutures for the report.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@anthropic-ai/sdk`	≥ 0.79.0&&< 0.91.1	0.91.1

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/sdk. 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/sdk to 0.91.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p7fg-763f-g4gf 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-p7fg-763f-g4gf 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-p7fg-763f-g4gf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The `BetaLocalFilesystemMemoryTool` in the Anthropic TypeScript SDK created memory files and directories using the Node.js default modes (`0o666` for files, `0o777` for directories), leaving them world-readable on systems with a standard umask and world-writable in environments with a permissive umask such as many Docker base images. A local attacker on a shared host could read persisted agent state, and in containerized deployments could modify memory files to influence subsequent model behavior. Users on the affected versions are advised to update to the latest version. Claude SDK thanks

O3 Security · Impact-Aware SCA

Is GHSA-p7fg-763f-g4gf in your dependencies?

O3 detects GHSA-p7fg-763f-g4gf 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