CVE-2026-34451: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in anthropics anthropic-sdk-typescript
CVE-2026-34451 is a path traversal vulnerability in the anthropic-sdk-typescript versions 0. 79. 0 to before 0. 81. 0. The vulnerability arises from improper validation of filesystem paths in the local filesystem memory tool, where a string prefix check without a trailing path separator allowed crafted paths to escape the intended sandbox directory. This flaw can be exploited via prompt injection to read or write files outside the restricted directory. The issue has been patched in version 0. 81. 0.
AI Analysis
Technical Summary
The vulnerability CVE-2026-34451 affects the anthropic-sdk-typescript, specifically versions from 0.79.0 up to but not including 0.81.0. This SDK provides server-side TypeScript or JavaScript applications access to the Claude API. The local filesystem memory tool within the SDK attempts to sandbox file operations by validating paths supplied by the model. However, the validation logic used a string prefix check that did not append a trailing path separator, which is a critical oversight. This allowed an attacker, via prompt injection, to supply a crafted pathname that resolved to a directory outside the intended sandboxed memory directory but sharing a prefix with it. Essentially, the path traversal vulnerability (CWE-22) enables unauthorized read and write operations on the filesystem outside the restricted directory. This could lead to exposure or modification of sensitive files, potentially impacting confidentiality and integrity. The vulnerability was patched in version 0.81.0 by correcting the path validation logic to properly restrict access to the sandbox directory. The CVSS 4.0 vector indicates the attack is network-based, requires no privileges or user interaction, but has high attack complexity and limited impact on confidentiality and integrity, with no impact on availability. No known exploits have been reported in the wild, but the vulnerability represents a significant risk for applications using the affected SDK versions.
Potential Impact
The primary impact of this vulnerability is unauthorized access to the local filesystem beyond the intended sandbox directory. This can lead to exposure of sensitive data, unauthorized modification or deletion of files, and potential compromise of application integrity. For organizations, this could mean leakage of confidential information, tampering with application data, or even enabling further attacks if critical system files are accessed or altered. Since the vulnerability can be triggered via prompt injection, it increases the attack surface for adversaries who can influence model inputs. The medium CVSS score reflects moderate risk, but the actual impact depends on the deployment context and the sensitivity of accessible files. Organizations running server-side applications with the affected SDK versions are at risk, especially if they process untrusted inputs or deploy in environments with sensitive data. The lack of authentication requirement and user interaction makes exploitation feasible remotely, although the high attack complexity may limit widespread exploitation. Nonetheless, the potential for data breach and integrity compromise warrants immediate remediation.
Mitigation Recommendations
Organizations should upgrade the anthropic-sdk-typescript to version 0.81.0 or later, where the vulnerability is patched. Until upgrading, implement strict input validation and sanitization on any data that influences model prompts to reduce the risk of prompt injection attacks. Employ runtime monitoring and filesystem access controls to detect and prevent unauthorized file operations outside designated directories. Consider running the SDK and associated services with least privilege, restricting filesystem permissions to minimize potential damage from exploitation. Additionally, conduct code reviews and security testing focused on path validation logic in custom extensions or integrations. Deploy application-layer firewalls or runtime application self-protection (RASP) tools to detect anomalous filesystem access patterns. Maintain awareness of updates from the vendor and apply patches promptly. Finally, educate developers on secure coding practices related to path handling and sandboxing to prevent similar issues.
Affected Countries
United States, United Kingdom, Germany, France, Canada, Australia, Japan, South Korea, India, Netherlands, Sweden, Singapore
CVE-2026-34451: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in anthropics anthropic-sdk-typescript
Description
CVE-2026-34451 is a path traversal vulnerability in the anthropic-sdk-typescript versions 0. 79. 0 to before 0. 81. 0. The vulnerability arises from improper validation of filesystem paths in the local filesystem memory tool, where a string prefix check without a trailing path separator allowed crafted paths to escape the intended sandbox directory. This flaw can be exploited via prompt injection to read or write files outside the restricted directory. The issue has been patched in version 0. 81. 0.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2026-34451 affects the anthropic-sdk-typescript, specifically versions from 0.79.0 up to but not including 0.81.0. This SDK provides server-side TypeScript or JavaScript applications access to the Claude API. The local filesystem memory tool within the SDK attempts to sandbox file operations by validating paths supplied by the model. However, the validation logic used a string prefix check that did not append a trailing path separator, which is a critical oversight. This allowed an attacker, via prompt injection, to supply a crafted pathname that resolved to a directory outside the intended sandboxed memory directory but sharing a prefix with it. Essentially, the path traversal vulnerability (CWE-22) enables unauthorized read and write operations on the filesystem outside the restricted directory. This could lead to exposure or modification of sensitive files, potentially impacting confidentiality and integrity. The vulnerability was patched in version 0.81.0 by correcting the path validation logic to properly restrict access to the sandbox directory. The CVSS 4.0 vector indicates the attack is network-based, requires no privileges or user interaction, but has high attack complexity and limited impact on confidentiality and integrity, with no impact on availability. No known exploits have been reported in the wild, but the vulnerability represents a significant risk for applications using the affected SDK versions.
Potential Impact
The primary impact of this vulnerability is unauthorized access to the local filesystem beyond the intended sandbox directory. This can lead to exposure of sensitive data, unauthorized modification or deletion of files, and potential compromise of application integrity. For organizations, this could mean leakage of confidential information, tampering with application data, or even enabling further attacks if critical system files are accessed or altered. Since the vulnerability can be triggered via prompt injection, it increases the attack surface for adversaries who can influence model inputs. The medium CVSS score reflects moderate risk, but the actual impact depends on the deployment context and the sensitivity of accessible files. Organizations running server-side applications with the affected SDK versions are at risk, especially if they process untrusted inputs or deploy in environments with sensitive data. The lack of authentication requirement and user interaction makes exploitation feasible remotely, although the high attack complexity may limit widespread exploitation. Nonetheless, the potential for data breach and integrity compromise warrants immediate remediation.
Mitigation Recommendations
Organizations should upgrade the anthropic-sdk-typescript to version 0.81.0 or later, where the vulnerability is patched. Until upgrading, implement strict input validation and sanitization on any data that influences model prompts to reduce the risk of prompt injection attacks. Employ runtime monitoring and filesystem access controls to detect and prevent unauthorized file operations outside designated directories. Consider running the SDK and associated services with least privilege, restricting filesystem permissions to minimize potential damage from exploitation. Additionally, conduct code reviews and security testing focused on path validation logic in custom extensions or integrations. Deploy application-layer firewalls or runtime application self-protection (RASP) tools to detect anomalous filesystem access patterns. Maintain awareness of updates from the vendor and apply patches promptly. Finally, educate developers on secure coding practices related to path handling and sandboxing to prevent similar issues.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-27T18:18:14.895Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69cc424fe6bfc5ba1d44f4b4
Added to database: 3/31/2026, 9:53:19 PM
Last enriched: 3/31/2026, 10:09:33 PM
Last updated: 3/31/2026, 10:58:11 PM
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.