dbcve.org
Conda BuildApplication · Anaconda

CVE-2025-32798

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-16
Fix available
A fix is available. Upgrade to 25.4.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Conda-build versions prior to 25.4.0 use the unsafe eval() function to process recipe selectors embedded in meta.yaml files. This allows arbitrary Python code execution during the build process because user-controlled selector expressions are evaluated without sanitization, compromising the integrity of the build environment.

MitigationUpgrade to conda-build version 25.4.0 or later to patch the unsafe eval() usage, and audit existing meta.yaml recipes for malicious selector expressions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Conda BuildApplication
Affected:< 25.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed conda-build version
    Run `conda list conda-build` or `conda-build --version` to see the currently installed version
    Affected if Version is lower than 25.4.0 (e.g., 25.3.0, 24.x, etc.)
  2. Verify conda-build is present
    Run `conda list | grep conda-build` to confirm conda-build is installed in the current environment
    Affected if conda-build appears in the list but is version 25.4.0 or lower
  3. Identify if building from conda recipes
    Check for the presence of meta.yaml files in your build workflow or repository, typically in a `recipe/` directory
    Affected if You build packages using conda-build and process meta.yaml files with selector expressions
  4. Check for selector expressions in meta.yaml
    Inspect any meta.yaml files you use for lines containing selectors like `#[linux]`, `#[py>=3.8]`, or other bracket-based selector syntax
    Affected if meta.yaml files contain selector expressions that get evaluated during the build process

You are affected if conda-build version is below 25.4.0 AND you build packages from conda recipes containing selector expressions in meta.yaml files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 25.4.0 or later
Fixed in 25.4.0
Vendor patch github.com →
Interim mitigation

Upgrade to conda-build version 25.4.0 or later to patch the unsafe eval() usage, and audit existing meta.yaml recipes for malicious selector expressions.

Recommended fix High confidence

25.4.0

  1. Upgrade conda-build to version 25.4.0 or later by running: pip install --upgrade conda-build or conda install -c conda-forge conda-build>=25.4.0
  2. Verify the installed version by running: conda-build --version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Conda Build Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32798 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32798 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data