CVE-2025-31484
conda-forge infrastructure uses a bad token for Azure's cf-staging access
We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
conda-forge infrastructure uses a bad token for Azure's cf-staging access
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.
Reserved 2025-03-28 | Published 2025-04-02 | Updated 2025-04-03 | Assigner GitHub_MCWE-284: Improper Access Control
github.com/...ucture/security/advisories/GHSA-m4h2-49xf-vq72
github.com/...ommit/70f3f09e64968d5f0a7b0525846f17cad42dd052
Support options
