Critical severity · published Apr 2, 2025
CVE-2025-31484
conda-forge infrastructure uses a bad token for Azure's cf-staging access
9.3
CVSS
0.4%
EPSS
No
On KEV
Description
conda-forge infrastructure holds common configurations and settings for key pieces of the conda-forge infrastructure.
Between 2025-02-10 and 2025-04-01, conda-forge infrastructure used the wrong token for Azure's cf-staging access. This bug meant that any feedstock maintainer could upload a package to the conda-forge channel, bypassing our feedstock-token + upload process. The security logs on anaconda.org were check for any packages that were not copied from the cf-staging to the conda-forge channel and none were found.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.4% · higher than 36% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
IN
infrastructure · conda-forge
>= 2025-02-10, <= 2025-04-01 · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-31484
CVE.org
https://www.cve.org/CVERecord?id=CVE-2025-31484
github.com
https://github.com/conda-forge/infrastructure/commit/70f3f09e64968d5f0a7b0525846f17cad42dd052
github.com
https://github.com/conda-forge/infrastructure/security/advisories/GHSA-m4h2-49xf-vq72
