Vulnerability 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.
Related Weaknesses (CWE)
References
- https://github.com/conda-forge/infrastructure/commit/70f3f09e64968d5f0a7b0525846
- https://github.com/conda-forge/infrastructure/security/advisories/GHSA-m4h2-49xf
FAQ
What is CVE-2025-31484?
CVE-2025-31484 is a documented vulnerability. 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...
How severe is CVE-2025-31484?
CVSS scoring is not yet available for CVE-2025-31484. Check NVD for updates.
Is there a patch for CVE-2025-31484?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.