CVE-2025-32800Network attack vector

Arbitrary code execution via unclaimed dependency namespace

Published Jun 16, 2025 · Updated Jun 17, 2025

Dependency confusion in Conda conda-build before 25.3.0 allows remote attackers to execute arbitrary code through a pip installation. The source tree's pyproject.toml declared conda-index as an installation dependency even though that name had no PyPI release, so pip could resolve attacker-controlled code. Exploitation requires an attacker to claim the namespace and a victim to install the project from source with dependency resolution enabled; the code then runs with the installing process's privileges.

CVSS severity9.8
Critical
EPSS probability0.60%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Dependency confusion in Conda conda-build before 25.3.0 allows remote attackers to execute arbitrary code through a pip installation. The source tree's pyproject.toml declared conda-index as an installation dependency even though that name had no PyPI release, so pip could resolve attacker-controlled code. Exploitation requires an attacker to claim the namespace and a victim to install the project from source with dependency resolution enabled; the code then runs with the installing process's privileges.

The record

CVE
CVE-2025-32800
Published
Jun 16, 2025
Updated
Jun 17, 2025
Vendor
Conda
Product
conda-build
Classifications
CWE-1357, T1195.001
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 16, 2025CVE publishedPublication date reported by the CVE source.
  2. 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.

  1. Affected versionversion=< 25.3.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Conda · conda-buildversion=< 25.3.0

Published CVSS scores

7.2GitHub, Inc.CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U
9.8NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-1357Reliance on Insufficiently Trustworthy Component
T1195.001Compromise Software Dependencies and Development Tools

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