Insecure Default File Permissions in Local Filesystem Memory Tool
Medium4.8CVE-2026-34450 · Published Mar 31, 2026 · updated Apr 1, 2026
The local filesystem memory tool in the Anthropic Python SDK created memory files with mode 0o666, 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. Both the synchronous and asynchronous memory tool implementations were affected. Users on the affected versions are advised to update to the latest version. Thank you to [`lucasfutures`](https://hackerone.com/lucasfutures) on HackerOne for the report.
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| anthropic PyPI | >= 0.86.0, < 0.87.0 | 0.87.0 |
Details and references
More Anthropic advisories
All Anthropic| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Apr 24 | Trust Dialog Bypass via Git Worktree Spoofing Allows Arbitrary Code Execution | High7.7 | 2.1.84 |
| Apr 20 | Sandbox Escape via Symlink Following Allows Arbitrary File Write Outside Workspace | High7.7 | 2.1.64 |
| Apr 17 | Insecure System-Wide Configuration Loading Enables Local Privilege Escalation on Windows | Medium5.4 | 2.1.75 |
| Mar 31 | Memory Tool Path Validation Race Condition Allows Sandbox Escape | Medium5.8 | 0.87.0 |
| Mar 31 | Memory Tool Path Validation Allows Sandbox Escape to Sibling Directories | Medium6.3 | 0.81.0 |
| Mar 18 | Workspace Trust Dialog Bypass via Repo-Controlled Settings File | High7.7 | 2.1.53 |