- Top reward
- $10,000
- Top severity paid
- Critical
- Assets in scope
- 14
- Public CVEs
- 34
- Last change
At a glance
What to know before you start testing.
- Pays up to $10,000
- for critical bugs.
- Report through their form
- hackerone.com/anthropic
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 3 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What HackerOne lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$10,000 from $3,000 |
| High |
|
$5,000 from $1,000 |
| Medium |
|
$2,500 from $250 |
| Low |
|
$750 from $100 |
- Response
-
Within 3 days
Acknowledge your submission within three (3) business days; and
- Safe harbor
-
Full
we will not pursue any legal action because of your research or responsible disclosure, subject to Anthropic's compliance with applicable laws and legal obligations.
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
14 assets you may test, 1 excluded.
Web 6
- anthropic.atlassian.com Critical
- api.anthropic.com Critical
- claude.ai Critical
- console.anthropic.com Critical
- docs.anthropic.com Critical
- support.anthropic.com Critical
Source code 1
- github.com/anthropics Critical
Products and areas 7
- API & SDKs Critical
- Claude Code Critical
- Claude Desktop Extensions and Claude.ai MCP servers Critical
- Claude in Chrome Critical
- Infrastructure & Internal Apps/Services Critical
- Leaked Employee API Keys Critical
- Official Clients Critical
Out of scope (1)
- https://github.com/modelcontextprotocol
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Anthropic (via HackerOne)'s policy.
While testing
-
Submit one vulnerability per report, unless you need to chain vulnerabilities to demonstrate impact.
-
You will avoid causing any harm to Anthropic's systems, including avoiding any data destruction, use, access, or acquisition
-
You will avoid exploiting any vulnerability beyond what is minimally required to reasonably prove that such potential vulnerability exists
-
You will not exfiltrate, download, or otherwise retain any data that you collect.
-
You must not perform any attacks that would compromise the security or confidentiality of any account that is not your own;
-
You must not perform any social engineering attacks (phishing, vishing, etc.) on any Anthropic employee, contractor, or representative;
-
You must not, as a condition of disclosure, require payment or compensation, or otherwise make threats to disclose the vulnerability in an irresponsible manner;
-
You must validate all vulnerabilities and provide a working proof of concept with your submission.
Not accepted
-
General security or email best practices, or missing best practices in SSL/TLS configurations, without a working proof of concept
-
Physical compromise or intrusions
-
Rate limiting or brute-force issues on non-authenticated endpoints
-
Compromises involving an insider
-
Social engineering (including phishing attempts)
-
Reflected file downloads
-
Account takeovers (including any brute-force attacks on accounts that are not your own)
-
Denial of service attacks
-
Clickjacking on pages with no sensitive actions
-
Missing HttpOnly or Secure flags on cookies
-
Dependency hijacking
-
Any widely publicized zero-day vulnerabilities that have no patch, or have only had a patch available for less than 30 days
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 56 minutes ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Rules updated
Added: “…s coordinated by Anthropic will be awarded at our discretion.”
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
| CVE | Summary | Severity | Published |
|---|---|---|---|
| CVE-2026-111497 | A buffer overflow vulnerability in the Brotli decoder (c/dec/decode.c) in Google Brotli versions 1.0.3 through 1.2.0 on all platforms allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream. Users need to update any Brotli librarie | Critical 9.2 | 22 Oct 2026 |
| CVE-2026-55607 | Claude Code is an agentic coding tool. From 2.1.38 until 2.1.163, Claude Code's worktree handling allowed creation of worktrees named ".git" and navigation to worktrees outside the sandbox context, enabling git directory confusion attacks. By exploiting symlink manipulation and git fsmonitor execution during worktree operations, an attacker could overwrite files in the user's home directory (such | High 7.7 | 29 Jun 2026 |
| CVE-2026-46406 | Claude Code is an agentic coding tool. From 2.1.59 until 2.1.128, the Claude Code /copy command wrote responses to a hardcoded, predictable path (/tmp/claude/response.md) without UID isolation, randomness, or symlink protection. The file was created world-readable (0644) in a world-traversable directory (0755), allowing any local user to read a privileged user's Claude response, which could contai | Medium 4.4 | 29 Jun 2026 |
| CVE-2026-54316 | Claude Code is an agentic coding tool. From 0.2.54 until 2.1.163, because the hostname huggingface.co was pre-approved as a bare hostname for the WebFetch tool, any path on that domain—including attacker-controlled model repositories—was auto-approved without a permission prompt or being subject to --allowedTools restrictions. An attacker able to inject untrusted content into a Claude Code context | Medium 6.0 | 23 Jun 2026 |
| CVE-2026-44467 | The Claude Desktop app gives you Claude Code with a graphical interface built for running multiple sessions side by side. From 1.2581.0 to before 1.4304.0, Claude Desktop's SSH remote development feature verified only whether a hostname existed in ~/.ssh/known_hosts without comparing the server's presented host key against the stored key. This allowed a network-positioned attacker to present an ar | High 7.4 | 13 May 2026 |
| CVE-2026-44470 | The Claude Desktop app gives you Claude Code with a graphical interface built for running multiple sessions side by side. Prior to 1.3834.0, the CoworkVMService component in Claude Desktop for Windows ran as SYSTEM and did not validate whether the VM bundle directory was a real directory or an NTFS directory junction before creating files within it. A local non-elevated user could replace the user | High 8.5 | 13 May 2026 |
| CVE-2026-40068 | In versions 2.1.63 through 2.1.83 of Claude Code, the folder trust determination logic used the git worktree commondir file without validating its contents. An attacker could craft a malicious repository with a commondir file pointing to a path the victim had previously trusted, causing Claude Code to bypass its trust confirmation dialog and immediately execute hooks defined in `.claude/settings.j | High 7.7 | 5 May 2026 |
| CVE-2026-41686 | Claude SDK for TypeScript provides access to the Claude API from server-side TypeScript or JavaScript applications. From version 0.79.0 to before version 0.91.1, the BetaLocalFilesystemMemoryTool in the Anthropic TypeScript SDK created memory files and directories using the Node.js default modes (0o666 for files, 0o777 for directories), leaving them world-readable on systems with a standard umask | Medium 4.8 | 4 May 2026 |
| CVE-2026-39861 | Claude Code is an agentic coding tool. Prior to version 2.1.64, Claude Code's sandbox did not prevent sandboxed processes from creating symlinks pointing to locations outside the workspace. When Claude Code subsequently wrote to a path within such a symlink, its unsandboxed process followed the symlink and wrote to the target location outside the workspace without prompting the user for confirmati | High 7.7 | 21 Apr 2026 |
| CVE-2026-35603 | Claude Code is an agentic coding tool. In versions prior to 2.1.75 on Windows, Claude Code loaded the system-wide default configuration from C:\ProgramData\ClaudeCode\managed-settings.json without validating directory ownership or access permissions. Because the ProgramData directory is writable by non-administrative users by default and the ClaudeCode subdirectory was not pre-created or access-re | Medium 5.4 | 17 Apr 2026 |
| CVE-2026-34450 | 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 | Medium 4.8 | 31 Mar 2026 |
| CVE-2026-34451 | Claude SDK for TypeScript provides access to the Claude API from server-side TypeScript or JavaScript applications. From version 0.79.0 to before version 0.81.0, the local filesystem memory tool in the Anthropic TypeScript SDK validated model-supplied paths using a string prefix check that did not append a trailing path separator. A model steered by prompt injection could supply a crafted path tha | Medium 6.3 | 31 Mar 2026 |
| CVE-2026-34452 | 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 async local filesystem memory tool in the Anthropic Python SDK validated that model-supplied paths resolved inside the sandboxed memory directory, but then returned the unresolved path for subsequent file operations. A local attacker able to write to the memory di | Medium 5.8 | 31 Mar 2026 |
| CVE-2026-22561 | Uncontrolled search path elements in Anthropic Claude for Windows installer (Claude Setup.exe) versions prior to 1.1.3363 allow local privilege escalation via DLL search-order hijacking. The installer loads DLLs (e.g., profapi.dll) from its own directory after UAC elevation, enabling arbitrary code execution if a malicious DLL is planted alongside the installer. | Medium 4.7 | 31 Mar 2026 |
| CVE-2026-33068 | 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 silen | High 7.7 | 20 Mar 2026 |
| CVE-2026-25724 | Claude Code is an agentic coding tool. Prior to version 2.1.7, Claude Code failed to strictly enforce deny rules configured in settings.json when accessing files through symbolic links. If a user explicitly denied Claude Code access to a file (such as /etc/passwd) and Claude Code had access to a symbolic link pointing to that file, it was possible for Claude Code to read the restricted file throug | Low 2.3 | 6 Feb 2026 |
| CVE-2026-25725 | Claude Code is an agentic coding tool. Prior to version 2.1.2, Claude Code's bubblewrap sandboxing mechanism failed to properly protect the .claude/settings.json configuration file when it did not exist at startup. While the parent directory was mounted as writable and .claude/settings.local.json was explicitly protected with read-only constraints, settings.json was not protected if it was missing | High 7.7 | 6 Feb 2026 |
| CVE-2026-25722 | Claude Code is an agentic coding tool. Prior to version 2.0.57, Claude Code failed to properly validate directory changes when combined with write operations to protected folders. By using the cd command to navigate into sensitive directories like .claude, it was possible to bypass write protection and create or modify files without user confirmation. Reliably exploiting this required the ability | High 7.7 | 6 Feb 2026 |
| CVE-2026-25723 | Claude Code is an agentic coding tool. Prior to version 2.0.55, Claude Code failed to properly validate commands using piped sed operations with the echo command, allowing attackers to bypass file write restrictions. This vulnerability enabled writing to sensitive directories like the .claude folder and paths outside the project scope. Exploiting this required the ability to execute commands throu | High 7.7 | 6 Feb 2026 |
| CVE-2026-24052 | Claude Code is an agentic coding tool. Prior to version 1.0.111, Claude Code contained insufficient URL validation in its trusted domain verification mechanism for WebFetch requests. The application used a startsWith() function to validate trusted domains (e.g., docs.python.org, modelcontextprotocol.io), this could have enabled attackers to register domains like modelcontextprotocol.io.example.com | High 7.1 | 3 Feb 2026 |
| CVE-2026-24053 | Claude Code is an agentic coding tool. Prior to version 2.0.74, due to a Bash command validation flaw in parsing ZSH clobber syntax, it was possible to bypass directory restrictions and write files outside the current working directory without user permission prompts. Exploiting this required the user to use ZSH and the ability to add untrusted content into a Claude Code context window. This issue | High 7.7 | 3 Feb 2026 |
| CVE-2026-24887 | Claude Code is an agentic coding tool. Prior to version 2.0.72, due to an error in command parsing, it was possible to bypass the Claude Code confirmation prompt to trigger execution of untrusted commands through the find command. Reliably exploiting this required the ability to add untrusted content into a Claude Code context window. This issue has been patched in version 2.0.72. | High 7.7 | 3 Feb 2026 |
| CVE-2026-21852 | Claude Code is an agentic coding tool. Prior to version 2.0.65, vulnerability in Claude Code's project-load flow allowed malicious repositories to exfiltrate data including Anthropic API keys before users confirmed trust. An attacker-controlled repository could include a settings file that sets ANTHROPIC_BASE_URL to an attacker-controlled endpoint and when the repository was opened, Claude Code wo | Medium 5.3 | 21 Jan 2026 |
| CVE-2025-66032 | Claude Code is an agentic coding tool. Prior to 1.0.93, Due to errors in parsing shell commands related to $IFS and short CLI flags, it was possible to bypass the Claude Code read-only validation and trigger arbitrary code execution. Reliably exploiting this requires the ability to add untrusted content into a Claude Code context window. This vulnerability is fixed in 1.0.93. | High 8.7 | 3 Dec 2025 |
| CVE-2025-64755 | Claude Code is an agentic coding tool. Prior to version 2.0.31, due to an error in sed command parsing, it was possible to bypass the Claude Code read-only validation and write to arbitrary files on the host system. This issue has been patched in version 2.0.31. | High 8.7 | 21 Nov 2025 |
| CVE-2025-65099 | Claude Code is an agentic coding tool. Prior to version 1.0.39, when running on a machine with Yarn 3.0 or above, Claude Code could have been tricked to execute code contained in a project via yarn plugins before the user accepted the startup trust dialog. Exploiting this would have required a user to start Claude Code in an untrusted directory and to be using Yarn 3.0 or above. This issue has bee | High 7.7 | 19 Nov 2025 |
| CVE-2025-59829 | Claude Code is an agentic coding tool. Versions below 1.0.120 failed to account for symlinks when checking permission deny rules. If a user explicitly denied Claude Code access to a file and Claude Code had access to a symlink pointing to that file, it was possible for Claude Code to access the file. Users on standard Claude Code auto-update will have received this fix automatically. Users perform | Low 2.3 | 3 Oct 2025 |
| CVE-2025-59536 | Claude Code is an agentic coding tool. Versions before 1.0.111 were vulnerable to Code Injection due to a bug in the startup trust dialog implementation. Claude Code could be tricked to execute code contained in a project before the user accepted the startup trust dialog. Exploiting this requires a user to start Claude Code in an untrusted directory. Users on standard Claude Code auto-update will | High 8.7 | 3 Oct 2025 |
| CVE-2025-59828 | Claude Code is an agentic coding tool. Prior to Claude Code version 1.0.39, when using Claude Code with Yarn versions 2.0+, Yarn plugins are auto-executed when running yarn --version. This could lead to a bypass of the directory trust dialog in Claude Code, as plugins would be executed prior to the user accepting the risks of working in an untrusted directory. Users running Yarn Classic were unaff | High 7.7 | 24 Sep 2025 |
| CVE-2025-59041 | Claude Code is an agentic coding tool. At startup, Claude Code executed a command templated in with `git config user.email`. Prior to version 1.0.105, a maliciously configured user email in git could be used to trigger arbitrary code execution before a user accepted the workspace trust dialog. Users on standard Claude Code auto-update will have received this fix automatically. Users performing man | High 8.7 | 10 Sep 2025 |
| CVE-2025-58764 | Claude Code is an agentic coding tool. Due to an error in command parsing, versions prior to 1.0.105 were vulnerable to a bypass of the Claude Code confirmation prompt to trigger execution of an untrusted command. Reliably exploiting this requires the ability to add untrusted content into a Claude Code context window. Users on standard Claude Code auto-update will have received this fix automatica | High 8.7 | 10 Sep 2025 |
| CVE-2025-55284 | Claude Code is an agentic coding tool. Prior to version 1.0.4, it's possible to bypass the Claude Code confirmation prompts to read a file and then send file contents over the network without user confirmation due to an overly broad allowlist of safe commands. Reliably exploiting this requires the ability to add untrusted content into a Claude Code context window. Users on standard Claude Code aut | High 7.1 | 16 Aug 2025 |
| CVE-2025-54794 | Claude Code is an agentic coding tool. In versions below 0.2.111, a path validation flaw using prefix matching instead of canonical path comparison, makes it possible to bypass directory restrictions and access files outside the CWD. Successful exploitation depends on the presence of (or ability to create) a directory with the same prefix as the CWD and the ability to add untrusted content into a | High 7.7 | 5 Aug 2025 |
| CVE-2025-54795 | Claude Code is an agentic coding tool. In versions below 1.0.20, an error in command parsing makes it possible to bypass the Claude Code confirmation prompt to trigger execution of an untrusted command. Reliably exploiting this requires the ability to add untrusted content into a Claude Code context window. This is fixed in version 1.0.20. | High 8.7 | 5 Aug 2025 |
Original policy
Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
The security of our systems and user data is Anthropic's top priority. We appreciate the work of security researchers acting in good faith to identify and report potential vulnerabilities. Involving researchers through our bug bounty program helps us continuously improve our security as our products reach a wider audience.
We look forward to partnering with you to further strengthen Anthropic's security!
Program Rules
Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
- To help us investigate and confirm bug bounty reports, you must use your
@wearehackerone.comemail address when creating any accounts and add aX-HackerOne-Handle: <your handle>header to your requests. - Submit one vulnerability per report, unless you need to chain vulnerabilities to demonstrate impact.
- When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
- Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
- Reports that lead to updating documentation to describe security risks will be awarded at our discretion with a $100 bounty.
- Reports in products or features that are released in Research Preview or Beta status will be treated as non-core for a 1-month period following their initial release.
- Reports of public zero-day vulnerabilities that have had an official patch for less than 7 days will be awarded on a case-by-case basis.
- False-positive and/or theoretical reports from automated scanners or written by AI will be closed as "Not Applicable" at Anthropic's discretion. You must validate all vulnerabilities and provide a working proof of concept with your submission.
- By submitting a report, you represent that you are the rightful author of the underlying work and grant Anthropic full rights to use the vulnerability report data (including sharing details with third parties as needed) to address any vulnerabilities. Vulnerabilities fixed by third parties coordinated by Anthropic will be awarded at our discretion.
Important Notes
- We are currently working on a remediation project for vulnerabilities bypassing the Claude Code permission modal for command execution. We expect this to provide a more holistic fix for these issues. During this time we still welcome reports about this, but it is likely that reports will be closed as duplicates if they will be fixed by this effort.
- In auto-accept-edits mode Claude Code is able to modify all files in the CWD. In some cases other software on the machine may execute these files. This behavior is the responsibility of the user that enables auto-accept-edits mode and is not considered to be a vulnerability in Claude Code.
- GitHub Action vulnerabilities in in-scope repos are treated as non-core vulnerabilities unless they can be shown to impact assets that are otherwise defined as core.
Out of Scope Findings
The following vulnerability classes are excluded from rewards, subject to Anthropic's discretion:
- General security or email best practices, or missing best practices in SSL/TLS configurations, without a working proof of concept
- Physical compromise or intrusions
- Rate limiting or brute-force issues on non-authenticated endpoints
- Compromises involving an insider
- Social engineering (including phishing attempts)
- Reflected file downloads
- Account takeovers (including any brute-force attacks on accounts that are not your own)
- Denial of service attacks
- Clickjacking on pages with no sensitive actions
- Missing HttpOnly or Secure flags on cookies
- Dependency hijacking
- Any widely publicized zero-day vulnerabilities that have no patch, or have only had a patch available for less than 30 days
Model Safety and Red Teaming
This bug bounty program is focused on identifying vulnerabilities in our infrastructure and code. Issues related to model content and responses — including jailbreaks, harmful content generation, and hallucinations — are out of scope for this program.
We are, however, always looking for ways to enhance the safety and harmlessness of our models.
If your report demonstrates a jailbreak of the Fable model family, please submit it to our dedicated bug bounty program at https://hackerone.com/anthropic-cyber-jailbreak. If you encounter safety issues, jailbreaks, or similar concerns, in any other model please email [email protected] with enough detail for us to replicate the issue.
Research Guidelines
While we reserve final and sole discretion for whether you are acting in good faith and in accordance with this Policy, we will generally presume you are acting in good faith if you abide by this Policy and agree to the following:
- You are testing Anthropic's systems for the sole purpose of identifying or discovering a potential vulnerability or any associated indicator of a vulnerability and reporting such information to us;
- You will avoid causing any harm to Anthropic's systems, including avoiding any data destruction, use, access, or acquisition; disruption of these systems or any customer user experience (including initiating denial of service attacks or using tools that generate substantial amounts of traffic); violation or compromise of the privacy or security of our customers, employees, or other users; or other illegal or harmful activities;
- You will avoid exploiting any vulnerability beyond what is minimally required to reasonably prove that such potential vulnerability exists, including avoiding accessing, acquiring, or using data that may be accessible from exploiting the vulnerability;
- You will avoid accessing, acquiring, or using the content of any communications, data, or information transmitted or stored on Anthropic's systems, unless such access is inadvertent;
- You will not exfiltrate, download, or otherwise retain any data that you collect. If you inadvertently access any data, you will report such access to us as part of your report;
- You must not perform any attacks that would compromise the security or confidentiality of any account that is not your own;
- You must not perform any social engineering attacks (phishing, vishing, etc.) on any Anthropic employee, contractor, or representative;
- You must not, as a condition of disclosure, require payment or compensation, or otherwise make threats to disclose the vulnerability in an irresponsible manner;
- You must not be listed on the Specially Designated Nationals and Blocked Persons List as published by the U.S. Treasury Department's Office of Foreign Assets Control ("OFAC") or any other sanctions list, or reside in any country that has been sanctioned by the United States Government; and
- You, at all times, are in compliance with all applicable federal, state, and local laws in connection with your research activities.
If you have any questions about this Policy or whether your research is consistent with these guidelines, please contact [email protected].
Disclosure Policy
- Please follow HackerOne's disclosure guidelines.
- We fully support researchers' right to publicly disclose vulnerabilities they discover. We ask only that you coordinate the timing of disclosure with us to prevent potential harm to our services, customers, and other parties. Please do not disclose the existence of or any details relating to a discovered vulnerability to a third party or to the public until you have received written confirmation from us.
- Researchers are free to report similar vulnerabilities in other organizations' services — we will never attempt to restrict such disclosures.
Your Expectations of Us
All good-faith reports will be taken seriously. Upon promptly and responsibly reporting any potential vulnerability you have discovered, you can expect us to promptly evaluate your findings. If we determine (at our sole discretion) that a vulnerability exists, you can expect us to validate the existence of the vulnerability, confirm the same with you, and promptly take appropriate steps to address, mitigate, or remediate the vulnerability to the extent feasible. Additionally, we will:
- Protect your name and contact information and not disclose such information without your consent, unless required by lawful legal process, law, or court order;
- Refrain from taking legal action as set forth in the Safe Harbor section below;
- With your permission, attribute your name and contribution on any public disclosure we make;
- Acknowledge your submission within three (3) business days; and
- Make best efforts to keep you updated and promptly complete our investigation.
Safe Harbor
If you, in our sole determination, make a good-faith effort to research and disclose vulnerabilities in accordance with this Policy and the above Research Guidelines, we will not pursue any legal action because of your research or responsible disclosure, subject to Anthropic's compliance with applicable laws and legal obligations. To qualify for safe harbor, disclosures to us must be unconditional and may not involve extortion or threats.
Changes to this Policy
We reserve the right to make changes to this Policy at any time by publishing a new policy and amending the date of last update. Vulnerabilities disclosed prior to any update of this Policy will remain subject to the policy then in effect.