User-level command execution via evaluated install path
Published Jun 17, 2025 · Updated Jun 17, 2025
Command injection in Conda Constructor before 3.11.3 allows context-dependent attackers to execute shell commands through a crafted install path. The shell installer template passes the interactive user_prefix value to eval, causing command substitutions and metacharacters in the path to run as shell code. Exploitation requires a user to enter the crafted path explicitly, and commands run with that user's privileges rather than root.
Summary
What happened
Command injection in Conda Constructor before 3.11.3 allows context-dependent attackers to execute shell commands through a crafted install path. The shell installer template passes the interactive user_prefix value to eval, causing command substitutions and metacharacters in the path to run as shell code. Exploitation requires a user to enter the crafted path explicitly, and commands run with that user's privileges rather than root.
The record
- CVE
- CVE-2025-49823
- Published
- Jun 17, 2025
- Updated
- Jun 17, 2025
- Vendor
- Conda
- Product
- Constructor
- Classifications
- CWE-77, T1059.004, T1204
- Attack vector
- physical
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 17, 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=< 3.11.3
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
- Crafted installation-path command-injection 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