Code execution via unsanitized recipe selector evaluation
Published Jun 16, 2025 · Updated Jun 17, 2025
Code injection in Conda conda-build before 25.4.0 allows remote attackers to execute arbitrary code through malicious recipe selectors. The metadata.py recipe parser passes embedded selector expressions to Python eval() without sanitization, permitting imports and operating-system calls. Execution occurs when conda-build processes an attacker-controlled recipe, and commands run with the build process's privileges.
Summary
What happened
Code injection in Conda conda-build before 25.4.0 allows remote attackers to execute arbitrary code through malicious recipe selectors. The metadata.py recipe parser passes embedded selector expressions to Python eval() without sanitization, permitting imports and operating-system calls. Execution occurs when conda-build processes an attacker-controlled recipe, and commands run with the build process's privileges.
The record
- CVE
- CVE-2025-32798
- Published
- Jun 16, 2025
- Updated
- Jun 17, 2025
- Vendor
- Conda
- Product
- conda-build
- Classifications
- CWE-94, T1059.006
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 16, 2025CVE publishedPublication date reported by the CVE source.
- Jun 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 25.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Malicious meta.yaml recipe-selector proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo