CVE-2025-32798

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 51% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
60(Track*)
EG Risk 60/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

June 16, 2025

Last Modified

July 2, 2025

Advisory Details (3)

Auto-updated Aug 5, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

Arbitrary Code Execution via Malicious Recipe Selectors · Advisory · conda/conda-build · GitHub

https://github.com/conda/conda-build/security/advisories/GHSA-6cc8-c3c9-3rgr
github_commit Patch Available

commit 3d87213b8407 (conda/conda-build)

Patch available: conda/conda-build 25.4.0 (contains commit 3d87213b8407)

https://github.com/conda/conda-build/commit/3d87213b840774a24ab1733664d2b36664233754
generic

conda-build/conda_build/metadata.py at 834448b995eee02cf1c2e7ca97bcfa9affc77ee5 · conda/conda-build · GitHub

https://github.com/conda/conda-build/blob/834448b995eee02cf1c2e7ca97bcfa9affc77ee5/conda_build/metadata.py

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 108 total refreshes for this CVE.

  1. 2026-08-07 16:26 UTCEPSS rescore
  2. 2026-08-06 13:46 UTCEPSS rescore
  3. 2026-08-05 19:16 UTCEPSS rescore
  4. 2026-08-04 15:09 UTCEPSS rescore
  5. 2026-08-04 10:37 UTCEPSS rescore
  6. 2026-08-03 10:35 UTCEPSS rescore
  7. 2026-08-02 02:26 UTCEPSS rescore
  8. 2026-08-01 04:15 UTCEPSS rescore
  9. 2026-07-30 16:27 UTCEPSS rescore
  10. 2026-07-30 01:29 UTCEPSS rescore
  11. 2026-07-28 15:35 UTCEPSS rescore
  12. 2026-07-27 14:12 UTCEPSS rescore
  13. 2026-07-26 14:53 UTCEPSS rescore
  14. 2026-07-25 14:17 UTCEPSS rescore
  15. 2026-07-24 14:17 UTCEPSS rescore
  16. 2026-07-24 03:11 UTCOSV refresh
  17. 2026-07-23 02:53 UTCEG score recompute
  18. 2026-07-22 14:07 UTCEPSS rescore
  19. 2026-07-22 14:07 UTCEPSS rescore
  20. 2026-07-21 15:24 UTCEPSS rescore
  21. 2026-07-21 15:24 UTCEPSS rescore
  22. 2026-07-20 17:07 UTCEPSS rescore
  23. 2026-07-19 14:30 UTCEPSS rescore
  24. 2026-07-19 14:30 UTCEPSS rescore
  25. 2026-07-19 02:28 UTCEPSS rescore
Show 75 more
  1. 2026-07-19 02:28 UTCEPSS rescore
  2. 2026-07-18 10:04 UTCEPSS rescore
  3. 2026-07-18 10:04 UTCEPSS rescore
  4. 2026-07-16 17:02 UTCEPSS rescore
  5. 2026-07-15 16:57 UTCEPSS rescore
  6. 2026-07-15 16:57 UTCEPSS rescore
  7. 2026-07-15 01:59 UTCEPSS rescore
  8. 2026-07-15 01:59 UTCEPSS rescore
  9. 2026-07-13 22:29 UTCEPSS rescore
  10. 2026-07-13 06:12 UTCEPSS rescore
  11. 2026-07-13 06:12 UTCEPSS rescore
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-12 05:46 UTCEPSS rescore
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-09 19:09 UTCEPSS rescore
  17. 2026-07-08 15:14 UTCEPSS rescore
  18. 2026-07-07 13:45 UTCEPSS rescore
  19. 2026-07-06 22:34 UTCOSV refresh
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 16:26 UTCEPSS rescore
  22. 2026-07-06 02:22 UTCEPSS rescore
  23. 2026-07-05 02:30 UTCEPSS rescore
  24. 2026-07-04 06:30 UTCEPSS rescore
  25. 2026-07-02 17:01 UTCEPSS rescore
  26. 2026-07-01 15:06 UTCEPSS rescore
  27. 2026-06-30 23:22 UTCEPSS rescore
  28. 2026-06-30 23:21 UTCEPSS rescore
  29. 2026-06-29 14:06 UTCEPSS rescore
  30. 2026-06-28 14:07 UTCEPSS rescore
  31. 2026-06-28 14:07 UTCEPSS rescore
  32. 2026-06-28 04:55 UTCEPSS rescore
  33. 2026-06-28 04:55 UTCEPSS rescore
  34. 2026-06-27 03:08 UTCEPSS rescore
  35. 2026-06-25 13:49 UTCEPSS rescore
  36. 2026-06-25 13:49 UTCEPSS rescore
  37. 2026-06-24 14:04 UTCEPSS rescore
  38. 2026-06-24 14:04 UTCEPSS rescore
  39. 2026-06-23 21:32 UTCEPSS rescore
  40. 2026-06-23 21:32 UTCEPSS rescore
  41. 2026-06-22 14:25 UTCEPSS rescore
  42. 2026-06-22 14:25 UTCEPSS rescore
  43. 2026-06-21 14:56 UTCEPSS rescore
  44. 2026-06-21 14:56 UTCEPSS rescore
  45. 2026-06-21 01:59 UTCEPSS rescore
  46. 2026-06-21 01:59 UTCEPSS rescore
  47. 2026-06-19 19:25 UTCEPSS rescore
  48. 2026-06-19 19:25 UTCEPSS rescore
  49. 2026-06-18 17:52 UTCEPSS rescore
  50. 2026-06-18 17:52 UTCEPSS rescore
  51. 2026-06-18 09:44 UTCOSV refresh
  52. 2026-06-17 17:52 UTCEPSS rescore
  53. 2026-06-16 17:52 UTCEPSS rescore
  54. 2026-06-16 17:52 UTCEPSS rescore
  55. 2026-06-15 17:48 UTCEPSS rescore
  56. 2026-06-14 23:17 UTCEPSS rescore
  57. 2026-06-13 23:00 UTCEPSS rescore
  58. 2026-06-13 23:00 UTCEPSS rescore
  59. 2026-06-12 23:11 UTCEPSS rescore
  60. 2026-06-11 13:59 UTCEPSS rescore
  61. 2026-06-10 22:18 UTCEPSS rescore
  62. 2026-06-10 13:22 UTCEPSS rescore
  63. 2026-06-08 14:16 UTCEPSS rescore
  64. 2026-06-08 14:16 UTCEPSS rescore
  65. 2026-06-07 15:24 UTCEPSS rescore
  66. 2026-06-07 15:24 UTCEPSS rescore
  67. 2026-06-06 13:47 UTCEPSS rescore
  68. 2026-06-06 13:47 UTCEPSS rescore
  69. 2026-06-05 22:46 UTCEPSS rescore
  70. 2026-06-05 22:46 UTCEPSS rescore
  71. 2026-06-05 06:10 UTCEPSS rescore
  72. 2026-06-05 06:10 UTCEPSS rescore
  73. 2026-06-04 13:12 UTCEPSS rescore
  74. 2026-06-04 13:11 UTCEPSS rescore
  75. 2026-06-02 20:12 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-32798?
CVE-2025-32798 is a critical vulnerability published on June 16, 2025. 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…
When was CVE-2025-32798 disclosed?
CVE-2025-32798 was first published in the National Vulnerability Database on June 16, 2025, with the most recent update on July 2, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-32798 actively exploited?
CVE-2025-32798 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 50.4% of all scored CVEs.
What is the CVSS score of CVE-2025-32798?
CVE-2025-32798 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-32798?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-32798, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-32798

Explore →

Is Your Infrastructure Affected by CVE-2025-32798?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs