CVE-2025-31484 conda-forge infrastructure uses a bad token for Azure's cf-staging access
Incorrect Azure token allowed feedstock maintainers to bypass upload processes and publish packages directly to the conda-forge channel.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-31484?
CVE-2025-31484 is a critical missing authorization vulnerability in conda-forge infrastructure, published on 2 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-284
Which versions are affected by CVE-2025-31484?
How do I fix CVE-2025-31484?
No fix has been published for CVE-2025-31484 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2025-31484 being exploited?
There is no known exploitation of CVE-2025-31484 in the wild and no public exploit code.
Sources
Also known as GHSA-m4h2-49xf-vq72.