Claude Sdk For Python EUVD-2026-17681

CVSS score of 5.8 reflects moderate risk (local attack vector, high privilege requirement at layer L, high confidentiality impact). However, EPSS and exploitation probability are not provided in this dataset. The vulnerability requires local filesystem access and authenticated SDK usage, substantially limiting threat surface compared to remote exploits. Real-world impact depends on deployment context: in multi-tenant or shared-host scenarios where untrusted users can write to the memory directory, this is a meaningful information disclosure risk. The TOCTOU nature means exploitation requires precise timing or repeated attempts, increasing attack complexity (AC:H in CVSS). No public exploit code or active exploitation signals are evident, but the straightforward nature of symlink manipulation suggests proof-of-concept development is trivial. Remediation is simple (upgrade to 0.87.0), making this a moderate-priority patch rather than critical-prioritize if hosting multi-user Python SDK applications on shared infrastructure.

An attacker with local shell access and write permissions to an application's memory directory monitors the directory for in-flight file operations. When the async memory tool validates a path like /memory/data.txt, the attacker quickly replaces a symlink pointing to /memory/data.txt with one targeting /etc/passwd or another sensitive file. The validation passes (the symlink initially pointed inside the sandbox), but the file read returns contents from /etc/passwd, disclosing sensitive configuration data. Alternatively, a write operation could corrupt or modify files outside the sandbox. Exploitation requires precise timing (AC:H) but is feasible in environments with predictable workload patterns or via polling techniques.