# CVE-2025-32798: Conda-build Allows Arbitrary Code Execution via Malicious Recipe Selectors

> Attackers can execute arbitrary code by crafting malicious recipe selectors in conda-build, compromising the build environment.

- **Severity:** High 8.2 (`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:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2025
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-6cc8-c3c9-3rgr

## What is CVE-2025-32798?

CVE-2025-32798 is a high-severity code injection vulnerability in conda-build, published on 16 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2025-32798?

It affects 1 product.


Products: Anaconda Conda-Build.

## How do I fix CVE-2025-32798?

No fix has been published for CVE-2025-32798 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-32798 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32798 exists.

## Other vulnerabilities in conda-build

- [CVE-2025-32800](https://insights.sbomify.com/CVE-2025-32800/): Supply chain in conda-build (high 7.2)
- [CVE-2025-32797](https://insights.sbomify.com/CVE-2025-32797/): Conda-build Insecure Build Script Permissions Enabling Arbitrary Code Execution (medium 6.0)
- [CVE-2025-32799](https://insights.sbomify.com/CVE-2025-32799/): Conda-build Vulnerable to Path Traversal via Malicious Tar File (medium 5.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32798 and fix it if it is affected.

What it is: CVE-2025-32798 is a high-severity code injection vulnerability in conda-build, published on 16 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32798 exists.

Affected product: conda-build. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-32798/ (Markdown: https://insights.sbomify.com/CVE-2025-32798/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32798
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32798
- OSV: https://osv.dev/vulnerability/CVE-2025-32798

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-32798/
Summaries are generated and may contain mistakes; the official description above is the record.