CVE-2025-31484

See a problem?
Please try reporting it to the source first.

Source

https://cve.org/CVERecord?id=CVE-2025-31484

Import Source

https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-31484.json

JSON Data

https://api.osv.dev/v1/vulns/CVE-2025-31484

Aliases

GHSA-m4h2-49xf-vq72

Published

2025-04-02T21:38:03.493Z

Modified

2026-04-02T12:46:49.060930Z

Severity

9.3 (Critical) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N CVSS Calculator

Summary

conda-forge infrastructure uses a bad token for Azure's cf-staging access

Details

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.

Database specific

{
    "cwe_ids": [
        "CWE-284"
    ],
    "cna_assigner": "GitHub_M",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/31xxx/CVE-2025-31484.json"
}

References

Affected packages

Git / github.com/conda-forge/infrastructure

Affected ranges

Type: GIT
Repo: https://github.com/conda-forge/infrastructure
Events: Introduced

0 Unknown introduced commit / All previous commits are affected

Fixed

70f3f09e64968d5f0a7b0525846f17cad42dd052

Database specific

source

"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-31484.json"