Anaconda Vulnerability Disclosure Program
By Anaconda Vulnerability disclosure program on Intigriti anaconda.com
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 1
- Public CVEs
- 10
- Last change
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report on Intigriti
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- No public write-ups
- Keep findings private.
Rewards
What Intigriti lists as the payout for each severity.
This program does not pay cash rewards.
- Pays cash
-
No
No, this is a vulnerability disclosure program. We do not offer financial rewards for vulnerability reports at this time.
Summarised with AI from the program policy on Intigriti, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test.
Web 1
- anaconda.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Anaconda Vulnerability Disclosure Program (via Intigriti)'s policy.
While testing
-
Respect the scope of the program
-
Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)
-
You can self-register on applicable Anaconda applications.
Not accepted
-
WordPress usernames disclosure
-
Pre-Auth Account takeover/OAuth squatting
-
Self-XSS that can't be used to exploit other users
-
Verbose messages/files/directory listings without disclosing any sensitive information
-
CORS misconfiguration on non-sensitive endpoints
-
Missing cookie flags
-
Missing security headers
-
Cross-site Request Forgery with no or low impact
-
Presence of autocomplete attribute on web forms
-
Reverse tabnabbing
-
Bypassing rate-limits or the non-existence of rate-limits
-
Best practices violations (password complexity, expiration, re-use, etc.)
-
Clickjacking without proven impact/unrealistic user interaction
-
CSV Injection
-
Sessions not being invalidated (logout, enabling 2FA, etc.)
-
Tokens leaked to third parties
-
Anything related to email spoofing, SPF, DMARC or DKIM
-
Content injection without being able to modify the HTML
-
Username/email enumeration
-
Email bombing
-
HTTP Request smuggling without any proven impact
-
Homograph attacks
-
XMLRPC enabled
-
Banner grabbing/Version disclosure
-
Not stripping metadata of files
Summarised with AI from the program policy on Intigriti, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 17 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.
-
Scope removed
anaconda.com
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
| CVE | Summary | Severity | Published |
|---|---|---|---|
| CVE-2026-23528 | Dask distributed is a distributed task scheduler for Dask. Prior to 2026.1.0, when Jupyter Lab, jupyter-server-proxy, and Dask distributed are all run together, it is possible to craft a URL which will result in code being executed by Jupyter due to a cross-side-scripting (XSS) bug in the Dask dashboard. It is possible for attackers to craft a phishing URL that assumes Jupyter Lab and Dask may be | Medium 5.3 | 16 Jan 2026 |
| CVE-2024-46060 | Anaconda3 macOS installers before 2024.06-1 contain a local privilege escalation vulnerability when installed outside the user's home directory. During installation, world-writable files are created and executed with root privileges. This allows a local low-privileged user to inject arbitrary commands, leading to code execution as the root user. | High 7.8 | 17 Dec 2025 |
| CVE-2025-32799 | Conda-build contains commands and tools to build conda packages. Prior to version 25.4.0, the conda-build processing logic is vulnerable to path traversal (Tarslip) attacks due to improper sanitization of tar entry paths. Attackers can craft tar archives containing entries with directory traversal sequences to write files outside the intended extraction directory. This could lead to arbitrary file | Medium 5.6 | 16 Jun 2025 |
| CVE-2025-32800 | Conda-build contains commands and tools to build conda packages. Prior to version 25.3.0, the pyproject.toml lists conda-index as a Python dependency. This package is not published in PyPI. An attacker could claim this namespace and upload arbitrary (malicious) code to the package, and then exploit pip install commands by injecting the malicious dependency in the solve. This issue has been fixed i | High 7.2 | 16 Jun 2025 |
| CVE-2025-32798 | Conda-build contains commands and tools to build conda packages. Prior to version 25.4.0, the conda-build recipe processing logic has been found to be vulnerable to arbitrary code execution due to unsafe evaluation of recipe selectors. Currently, conda-build uses the eval function to process embedded selectors in meta.yaml files. This approach evaluates user-defined expressions without proper sani | High 8.2 | 16 Jun 2025 |
| CVE-2025-32797 | Conda-build contains commands and tools to build conda packages. Prior to version 25.3.1, the write_build_scripts function in conda-build creates the temporary build script conda_build.sh with overly permissive file permissions (0o766), allowing write access to all users. Attackers with filesystem access can exploit a race condition to overwrite the script before execution, enabling arbitrary code | Medium 6.0 | 16 Jun 2025 |
| CVE-2023-35845 | Anaconda 3 2023.03-1-Linux allows local users to disrupt TLS certificate validation by modifying the cacert.pem file used by the installed pip program. This occurs because many files are installed as world-writable on Linux, ignoring umask, even when these files are installed as root. Miniconda is also affected. | Medium 4.7 | 11 Sep 2023 |
| CVE-2021-42969 | Certain Anaconda3 2021.05 are affected by OS command injection. When a user installs Anaconda, an attacker can create a new file and write something in usercustomize.py. When the user opens the terminal or activates Anaconda, the command will be executed. | High 8.8 | 13 May 2022 |
| CVE-2022-26526 | Anaconda Anaconda3 (Anaconda Distribution) through 2021.11.0.0 and Miniconda3 through 4.11.0.0 can create a world-writable directory under %PROGRAMDATA% and place that directory into the system PATH environment variable. Thus, for example, local users can gain privileges by placing a Trojan horse file into that directory. (This problem can only happen in a non-default installation. The person who | High 7.8 | 17 Mar 2022 |
| CVE-2021-42343 | An issue was discovered in the Dask distributed package before 2021.10.0 for Python. Single machine Dask clusters started with dask.distributed.LocalCluster or dask.distributed.Client (which defaults to using LocalCluster) would mistakenly configure their respective Dask workers to listen on external interfaces (typically with a randomly selected high port) rather than only on localhost. A Dask cl | Critical 9.8 | 26 Oct 2021 |
Original policy
Copied from www.intigriti.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Description
Anaconda is the trusted platform accelerating enterprise AI with governed open-source Python. We serve millions of users globally—from individual developers to Fortune 500 companies—powering AI/ML model development, data science workflows, and intelligent applications. Our platform provides pre-vetted Python packages, automated security scanning, and enterprise governance that helps organizations move from AI prototype to production faster, safer, and smarter.
What do we do? We provide enterprise-ready AI development tools and trusted Python package management solutions. Anaconda Core delivers secure, validated open-source packages with intelligent dependency resolution. Anaconda AI Catalyst enables rapid deployment of pre-validated, optimized AI models with built-in governance. Our platform helps organizations scale AI initiatives while maintaining security and compliance standards.
Intention for this program To collaborate with the community in identifying and addressing security vulnerabilities across Anaconda's infrastructure, products, and services. Your responsible disclosure helps us maintain the trust of millions of users who rely on our platform to advance their AI initiatives.
Rules of engagement
By participating in this program, you agree to:
- Respect the Community Code of Conduct
- Respect the Intigriti Terms and Conditions
- Respect the scope of the program
- Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)
You may not participate in this program if you are ordinarily resident in, or located in, any country or region subject to comprehensive sanctions, or if you are an individual or entity identified on any applicable sanctions list (including those administered by OFAC, the EU, the UN, or the UK's OFSI).
In scope
Introduction
Thank you for your interest in helping secure Anaconda's platform. This vulnerability disclosure program covers all Anaconda-owned web properties, infrastructure, applications, and installers. We welcome reports of critical and high security vulnerabilities that could impact our users or infrastructure.
Out of scope
Anaconda-Specific Exclusions
We will try our best to forward any non-Anaconda product vulnerabilities to the relevant owners.
- Open source projects not owned/maintained by Anaconda (e.g., conda, constructor, menuinst, conda-standalone when not part of Anaconda installers)
- Third-party dependencies with separate security programs
- Vulnerabilities in Python itself or other language runtimes
- Vulnerabilities in community-contributed Conda packages
- Social engineering attacks against Anaconda employees
- Physical security testing
- Testing that requires persistent access to production systems
- Tokenized/authenticated access to commercial repositories without authorization
- Known installer issues already documented in GitHub repositories
Application
- Windows single-user installations (not run as administrator) may have issues when uninstallation is run as administrator (registry entries, Start Menu entries remain). See conda/menuinst#341 and conda/constructor#997
- WordPress usernames disclosure
- Pre-Auth Account takeover/OAuth squatting
- Self-XSS that can't be used to exploit other users
- Verbose messages/files/directory listings without disclosing any sensitive information
- CORS misconfiguration on non-sensitive endpoints
- Missing cookie flags
- Missing security headers
- Cross-site Request Forgery with no or low impact
- Presence of autocomplete attribute on web forms
- Reverse tabnabbing
- Bypassing rate-limits or the non-existence of rate-limits
- Best practices violations (password complexity, expiration, re-use, etc.)
- Clickjacking without proven impact/unrealistic user interaction
- CSV Injection
- Sessions not being invalidated (logout, enabling 2FA, etc.)
- Tokens leaked to third parties
- Anything related to email spoofing, SPF, DMARC or DKIM
- Content injection without being able to modify the HTML
- Username/email enumeration
- Email bombing
- HTTP Request smuggling without any proven impact
- Homograph attacks
- XMLRPC enabled
- Banner grabbing/Version disclosure
- Not stripping metadata of files
- Same-site scripting
- Subdomain takeover without taking over the subdomain
- Arbitrary file upload without proof of the existence of the uploaded file
- Blind SSRF without proven business impact (pingbacks aren't sufficient)
- Disclosed/misconfigured Google Maps API keys
- Host header injection without proven business impact
Severity
This program follows Intigriti's triage standards based on the proof of concept.
FAQ
Where can we get credentials for testing?
You can self-register on applicable Anaconda applications.
Is this a bug bounty program?
No, this is a vulnerability disclosure program. We do not offer financial rewards for vulnerability reports at this time. We value responsible disclosure and will acknowledge your contributions to improving our security.