CVE-2026-33068: CWE-807: Reliance on Untrusted Inputs in a Security Decision in anthropics claude-code
Claude Code is an agentic coding tool. Versions prior to 2.1.53 resolved the permission mode from settings files, including the repo-controlled .claude/settings.json, before determining whether to display the workspace trust confirmation dialog. A malicious repository could set permissions.defaultMode to bypassPermissions in its committed .claude/settings.json, causing the trust dialog to be silently skipped on first open. This allowed a user to be placed into a permissive mode without seeing the trust confirmation prompt, making it easier for an attacker-controlled repository to gain tool execution without explicit user consent. This issue has been patched in version 2.1.53.
AI Analysis
Technical Summary
Anthropics claude-code is an agentic coding tool that, prior to version 2.1.53, determined its permission mode based on settings files, including the repository-controlled .claude/settings.json. This design flaw allowed a malicious repository to manipulate the permissions.defaultMode setting by setting it to bypassPermissions. When this occurs, the tool skips the workspace trust confirmation dialog that normally prompts users to confirm trust before enabling permissive execution modes. As a result, users opening such a repository would unknowingly enter a permissive mode, enabling the repository to execute potentially malicious code without explicit user approval. This vulnerability is classified under CWE-807, which involves reliance on untrusted inputs in security decisions. The CVSS 4.0 score of 7.7 reflects a high severity due to network attack vector, low attack complexity, partial attack and user interaction required, and high impact on confidentiality, integrity, and availability. The issue was addressed and patched in claude-code version 2.1.53 by removing reliance on untrusted repository-controlled settings for permission decisions.
Potential Impact
The vulnerability allows attacker-controlled repositories to bypass the workspace trust confirmation dialog, leading to silent elevation of permissions and enabling execution of potentially malicious code within the claude-code environment. This can compromise confidentiality, integrity, and availability of user projects and systems where claude-code is used. Organizations relying on claude-code for coding automation or agentic tasks risk unauthorized code execution, data leakage, or system compromise. Since the attack requires user interaction (opening a malicious repository), social engineering or supply chain attack vectors are likely. The scope includes all users running vulnerable versions (<2.1.53) who open attacker-controlled repositories. The absence of explicit user consent increases the risk of unnoticed compromise, which can facilitate further lateral movement or persistent threats within development environments.
Mitigation Recommendations
1. Upgrade anthropics claude-code to version 2.1.53 or later immediately to apply the patch that removes reliance on untrusted repository-controlled settings for permission decisions. 2. Implement strict repository vetting and code review policies to prevent malicious repositories from being introduced into development workflows. 3. Educate users about the risks of opening untrusted repositories and encourage verification of repository sources before use. 4. Employ endpoint security solutions that monitor and restrict unauthorized code execution within development environments. 5. Consider isolating development environments or using sandboxing techniques to limit the impact of potential malicious code execution. 6. Monitor logs and alerts for unusual activity related to claude-code usage, especially around permission changes or unexpected executions.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, Japan, South Korea, India, Netherlands
CVE-2026-33068: CWE-807: Reliance on Untrusted Inputs in a Security Decision in anthropics claude-code
Description
Claude Code is an agentic coding tool. Versions prior to 2.1.53 resolved the permission mode from settings files, including the repo-controlled .claude/settings.json, before determining whether to display the workspace trust confirmation dialog. A malicious repository could set permissions.defaultMode to bypassPermissions in its committed .claude/settings.json, causing the trust dialog to be silently skipped on first open. This allowed a user to be placed into a permissive mode without seeing the trust confirmation prompt, making it easier for an attacker-controlled repository to gain tool execution without explicit user consent. This issue has been patched in version 2.1.53.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Anthropics claude-code is an agentic coding tool that, prior to version 2.1.53, determined its permission mode based on settings files, including the repository-controlled .claude/settings.json. This design flaw allowed a malicious repository to manipulate the permissions.defaultMode setting by setting it to bypassPermissions. When this occurs, the tool skips the workspace trust confirmation dialog that normally prompts users to confirm trust before enabling permissive execution modes. As a result, users opening such a repository would unknowingly enter a permissive mode, enabling the repository to execute potentially malicious code without explicit user approval. This vulnerability is classified under CWE-807, which involves reliance on untrusted inputs in security decisions. The CVSS 4.0 score of 7.7 reflects a high severity due to network attack vector, low attack complexity, partial attack and user interaction required, and high impact on confidentiality, integrity, and availability. The issue was addressed and patched in claude-code version 2.1.53 by removing reliance on untrusted repository-controlled settings for permission decisions.
Potential Impact
The vulnerability allows attacker-controlled repositories to bypass the workspace trust confirmation dialog, leading to silent elevation of permissions and enabling execution of potentially malicious code within the claude-code environment. This can compromise confidentiality, integrity, and availability of user projects and systems where claude-code is used. Organizations relying on claude-code for coding automation or agentic tasks risk unauthorized code execution, data leakage, or system compromise. Since the attack requires user interaction (opening a malicious repository), social engineering or supply chain attack vectors are likely. The scope includes all users running vulnerable versions (<2.1.53) who open attacker-controlled repositories. The absence of explicit user consent increases the risk of unnoticed compromise, which can facilitate further lateral movement or persistent threats within development environments.
Mitigation Recommendations
1. Upgrade anthropics claude-code to version 2.1.53 or later immediately to apply the patch that removes reliance on untrusted repository-controlled settings for permission decisions. 2. Implement strict repository vetting and code review policies to prevent malicious repositories from being introduced into development workflows. 3. Educate users about the risks of opening untrusted repositories and encourage verification of repository sources before use. 4. Employ endpoint security solutions that monitor and restrict unauthorized code execution within development environments. 5. Consider isolating development environments or using sandboxing techniques to limit the impact of potential malicious code execution. 6. Monitor logs and alerts for unusual activity related to claude-code usage, especially around permission changes or unexpected executions.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-17T19:27:06.343Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69bd5190e32a4fbe5f99947e
Added to database: 3/20/2026, 1:54:24 PM
Last enriched: 3/20/2026, 2:09:00 PM
Last updated: 4/30/2026, 11:18:24 PM
Views: 173
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.
External Links
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.