CVE-2026-34450: Claude SDK for Python: Insecure Default File Permissions in Local Filesystem Memory Tool

Published Mar 31, 2026
·
Updated

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.

Other sources

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.

Claude SDK for Python thanks lucasfutures on HackerOne for the report.

GitHub

Affected Software

3 affected componentsFixes available
pypi/anthropic>=0.86.0<0.87.0
pip/anthropic>=0.86.0<0.87.0
0.87.0
Anthropic Claude Sdk For Python Python>=0.86.0<0.87.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/anthropic to a version that resolves this vulnerability.

    Fixed in 0.87.0
  2. Upgrade

    Upgrade Anthropic Python SDK (Claude SDK for Python) to a version that resolves this vulnerability.

    Fixed in 0.87.0
  3. Configuration

    Update to 0.87.0, which patches the local filesystem memory tool that previously created memory files with mode 0o666.

    Local filesystem memory tool (Anthropic Python SDK) memory files permission mode = 0o666 (world-readable/world-writable)

Event History

Mar 31, 2026
CVE Published
via MITRE·09:32 PM
Data Sourced
via MITRE·09:32 PM
DescriptionWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
RemedyAffected Software
Apr 1, 2026
Advisory Published
via GitHub·09:15 PM
Data Sourced
via GitHub·09:15 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-34450?

CVE-2026-34450 has been classified as a medium severity vulnerability due to insecure default file permissions.

2

How do I fix CVE-2026-34450?

To fix CVE-2026-34450, upgrade to the version 0.87.0 or later of the Claude SDK for Python.

3

What settings are affected by CVE-2026-34450?

CVE-2026-34450 affects the local filesystem memory tool used by the Claude SDK for Python.

4

In which versions of the Claude SDK does CVE-2026-34450 exist?

CVE-2026-34450 exists in the Claude SDK for Python from version 0.86.0 to before version 0.87.0.

5

What can happen if CVE-2026-34450 is exploited?

If CVE-2026-34450 is exploited, unauthorized access to sensitive files may occur due to insecure file permissions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203