CVE-2025-32800·Python vulnerability
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 in version 25.3.0. A workaround involves using --no-deps for pip install-ing the project from the repository.
- Severity
- critical
- Software
- Python
- Fixed in
- 25.3.0
- Published
- 2025-06-16
Affected versions
Until: 25.3.0
Fixed in: 25.3.0
How to fix this CVE
Upgrade conda-build to version 25.3.0 or later to eliminate the dependency namespace hijacking vulnerability. If immediate patching is not possible, install conda-build from the repository using pip install --no-deps to prevent malicious transitive dependency injection. Verify that no unauthorized packages have been pulled into your environment during the vulnerable window.
sudo dnf update python3-conda-buildDefensia detects this vulnerability
How to check if you are affected
- Step 1: Run `python3 -m pip show conda-build` to check the installed version and confirm it is below 25.3.0
- Step 2: Execute `pip list | grep conda-index` to detect if the malicious conda-index package has been installed in the current environment
- Step 3: Search your pip logs (typically in ~/.pip/pip.log or /var/log/apt/history.log) for unexpected installations of conda-index or unusual dependency resolution patterns
- Step 4: Verify the fix by running `python3 -c 'import conda_build; print(conda_build.__version__)` and confirming version >= 25.3.0
Indicators of compromise
- conda-index package downloaded from PyPI (non-official namespace)
- Unexpected imports of conda_index module in Python environments
- pip install logs showing conda-index resolution for conda-build < 25.3.0
FAQ
What is CVE-2025-32800?
CVE-2025-32800 is a namespace hijacking vulnerability in conda-build where the pyproject.toml references conda-index as a dependency, but this package is not published on PyPI. An attacker could register the abandoned namespace and push malicious code that gets installed during dependency resolution.
Is CVE-2025-32800 being actively exploited?
No, this vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits have been released, though the attack vector is straightforward and the impact is severe.
What versions of conda-build are affected by CVE-2025-32800?
All versions of conda-build prior to 25.3.0 are vulnerable. The fix was implemented in version 25.3.0 and later.
How do I check if my server is vulnerable to CVE-2025-32800?
Run `python3 -m pip show conda-build` and check if the version is less than 25.3.0. Additionally, run `pip list | grep conda-index` to see if the malicious package has already been installed.
Does Defensia detect CVE-2025-32800?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If conda-build is installed on a monitored server, CVE-2025-32800 will appear in your dashboard with remediation steps.
Related Python CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2025-32800. Free for 1 server.
Get started free