Arbitrary code execution via evaluated version assignment
Published Jun 13, 2025 · Updated Jun 13, 2025
Eval injection in conda-forge-ci-setup before 4.15.0 allows local users to execute arbitrary code through a crafted meta.yaml file. The setup.py version parser reads the file selected through RECIPE_DIR, extracts the version assignment, and passes the resulting expression directly to eval without sanitization. Exploitation requires control of RECIPE_DIR and the referenced recipe file in the build environment; successful execution runs with the setup process privileges.
Summary
What happened
Eval injection in conda-forge-ci-setup before 4.15.0 allows local users to execute arbitrary code through a crafted meta.yaml file. The setup.py version parser reads the file selected through RECIPE_DIR, extracts the version assignment, and passes the resulting expression directly to eval without sanitization. Exploitation requires control of RECIPE_DIR and the referenced recipe file in the build environment; successful execution runs with the setup process privileges.
The record
- CVE
- CVE-2025-49598
- Published
- Jun 13, 2025
- Updated
- Jun 13, 2025
- Vendor
- conda-forge
- Product
- conda-forge-ci-setup
- Classifications
- CWE-95, T1059.006
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 13, 2025CVE publishedPublication date reported by the CVE source.
- Jun 13, 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=< 4.15.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
- 7ASecurity meta.yaml eval 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