Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V13 - Configuration Default permission hardening
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | The CVSS score of 4.8 with vector AV:L/AC:L/PR:L reflects a local attack requiring low privileges and no user interaction, resulting in low confidentiality and integrity impacts. The EPSS score is not provided in the input data. The vulnerability is NOT listed in CISA KEV and no public exploit code is identified, indicating this is a lower-urgency issue from an exploitation perspective despite the clear security defect. However, real-world risk varies significantly by deployment context: in shared hosting environments or multi-tenant systems, local users could exfiltrate sensitive agent state or inject malicious instructions into AI model interactions, creating indirect but serious impact. In containerized deployments (highlighted as a specific attack vector), the risk is elevated if containers run with permissive umask or if multiple containers share a volume with world-writable permissions. The low CVSS score reflects the requirement for local access; however, the specific nature of the exposure-sensitive AI agent state and model behavior manipulation-warrants prompt patching despite the low numerical risk rating. |
| Exploit ScenarioDerived | On a shared Linux host or Docker container with a permissive umask, a local attacker running as a different user (or from another container with shared volume access) could enumerate the home directory or application data directory of a process using the affected SDK version, discover the memory files, read them to extract sensitive prompt histories and model instructions, and potentially modify them to inject adversarial instructions into subsequent AI model invocations. For example, in a multi-tenant container platform where volumes are shared, an attacker in one tenant's container could read or corrupt agent memory belonging to another tenant, compromising the confidentiality and integrity of AI-driven applications. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 31, 2026
Anthropic Python SDK versions 0.86.0 to before 0.87.0 create memory files with overly permissive file permissions (0o666), allowing local attackers to read persisted agent state or modify memory files to influence model behavior on shared hosts and Docker environments. The vulnerability affects both synchronous and asynchronous memory tool implementations and has been patched in version 0.87.0; no public exploit code or active exploitation has been identified at the time of analysis.
RemediationAI
Vendor-released patch: upgrade to Anthropic Python SDK version 0.87.0 or later. The patched version corrects file mode creation to use restrictive permissions (0o600 or equivalent) rather than 0o666, ensuring memory files are readable and writable only by the owning process. For users unable to immediately upgrade, review deployment architecture to restrict file system access to trusted users only and verify that shared host or container configurations do not expose memory file directories to unprivileged accounts. The upstream fix is documented in commit 715030ceb4d6dd8d3546e999c680e29532bf1255 available at https://github.com/anthropics/anthropic-sdk-python/commit/715030ceb4d6dd8d3546e999c680e29532bf1255.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in pypi, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability exists in the local filesystem memory tool component of the Anthropic Python SDK, which persists agent memory state to disk. The root cause is improper file mode specification (CWE-276: Incorrect Default Permissions) when creating these memory files. On Unix-like systems with standard umask (typically 0o022), files created with mode 0o666 become world-readable despite the umask; in permissive environments such as Docker base images with umask 0o000, these files become world-writable. This allows any local process running as a different user (but with file system access) to read or modify the persisted memory files. The CPE for affected product is cpe:2.4:a:anthropic:anthropic-sdk-python:*:*:*:*:*:python:*. Both the sync and async implementations of the memory tool were affected, indicating the vulnerability existed at a fundamental level in the file creation logic rather than isolated to one code path.
Know when Claude Sdk For Python gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Primary rating from Vendor (github) · only source for this CVE.
CVSS VectorVendor: github
Lifecycle Timeline
2DescriptionCVE.org
The Claude SDK for Python provides access to the Claude API from Python applications. From version 0.86.0 to before version 0.87.0, 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. This issue has been patched in version 0.87.0.
Blast Radius
ecosystem impact- 13 pypi packages depend on anthropic (10 direct, 3 indirect)
Ecosystem-wide dependent count for version 0.86.0.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
EUVD-2026-17677
GHSA-q5f5-3gjm-7mfm
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB