CVE-2025-32798: conda-build · Code Injection
Affects conda-buildSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 25.4.0 soon.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 25.4.0
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 16 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade conda-build to 25.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIconda-buildpkg:pypi/conda-buildOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediate upgrade to conda-build version 25.4.0 or later to ensure the vulnerability is patched. 2. Audit and restrict sources of meta.yaml recipe files to trusted repositories only; avoid using unverified or third-party recipes without thorough review. 3. Implement strict code review and validation processes for all build recipes to detect and remove potentially malicious selectors. 4. Use isolated and ephemeral build environments (e.g., containers or virtual machines) to limit the impact of any potential code execution during builds. 5. Monitor build logs and environment activity for unusual commands or file operations indicative of exploitation attempts. 6. Employ runtime application self-protection (RASP) or endpoint detection and response (EDR) tools to detect anomalous behavior during build processes. 7. Educate developers and build engineers about the risks of unsafe eval() usage and secure coding practices in build automation. 8. If upgrading is not immediately possible, consider disabling or sandboxing selector evaluation functionality where feasible to reduce risk.
Description
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 sanitization, which allows arbitrary code to be executed during the build process. As a result, the integrity of the build environment is compromised, and unauthorized commands or file operations may be performed. The vulnerability stems from the inherent risk of using eval() on untrusted input in a context intended to control dynamic build configurations. By directly interpreting selector expressions, conda-build creates a potential execution pathway for malicious code, violating security assumptions. This issue has been patched in version 25.4.0.
References
- github.com/conda/conda-build/security/advisories/GHSA-6cc8-c3c9-3rgr (opens in a new tab)
- github.com/conda/conda-build/commit/3d87213b840774a24ab1733664d2b36664233754 (opens in a new tab)
- github.com/conda/conda-build/blob/834448b995eee02cf1c2e7ca97bcfa9affc77ee5/conda_build/metadata.py (opens in a new tab)