Build-user code execution via writable script race
Published Jun 16, 2025 · Updated Jun 17, 2025
Insecure permissions in Conda conda-build before 25.3.1 allow local users to execute code as a build user through a script race. The write_build_scripts function creates conda_build.sh with mode 0766, permitting other filesystem users to replace it before execution. Exploitation requires local filesystem access and precise timing in a shared build directory, and successful replacement runs attacker-controlled shell code with the victim build user's privileges.
Summary
What happened
Insecure permissions in Conda conda-build before 25.3.1 allow local users to execute code as a build user through a script race. The write_build_scripts function creates conda_build.sh with mode 0766, permitting other filesystem users to replace it before execution. Exploitation requires local filesystem access and precise timing in a shared build directory, and successful replacement runs attacker-controlled shell code with the victim build user's privileges.
The record
- CVE
- CVE-2025-32797
- Published
- Jun 16, 2025
- Updated
- Jun 17, 2025
- Vendor
- Conda
- Product
- conda-build
- Classifications
- CWE-277, T1059.004
- Attack vector
- local
- Privileges
- Unavailable
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.3.1
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
No public exploit references are available in this record.
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