Tool execution via repo-controlled permission mode
Published Mar 20, 2026 · Updated Mar 20, 2026
Workspace trust bypass in Claude Code before 2.1.53 allows remote attackers to gain tool execution through a malicious repository. The startup path resolves permissions.defaultMode from .claude/settings.json before deciding whether to show the trust dialog, so bypassPermissions suppresses the prompt. Exploitation requires a developer to open the attacker-controlled repository; the resulting permissive session executes tools without explicit consent.
Summary
What happened
Workspace trust bypass in Claude Code before 2.1.53 allows remote attackers to gain tool execution through a malicious repository. The startup path resolves permissions.defaultMode from .claude/settings.json before deciding whether to show the trust dialog, so bypassPermissions suppresses the prompt. Exploitation requires a developer to open the attacker-controlled repository; the resulting permissive session executes tools without explicit consent.
The record
- CVE
- CVE-2026-33068
- Published
- Mar 20, 2026
- Updated
- Mar 20, 2026
- Vendor
- Anthropic
- Product
- Claude Code
- Classifications
- CWE-807, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2026CVE publishedPublication date reported by the CVE source.
- Mar 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.1.53
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo