# 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.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2025
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-m4h2-49xf-vq72

## 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 (Improper Access Control)

## 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.

## Is CVE-2025-31484 being exploited?

There is no known exploitation of CVE-2025-31484 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-31484 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2025-31484 in the wild and no public exploit code.

Affected product: conda-forge infrastructure. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-31484/ (Markdown: https://insights.sbomify.com/CVE-2025-31484/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-31484
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-31484
- OSV: https://osv.dev/vulnerability/CVE-2025-31484

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-31484/
Summaries are generated and may contain mistakes; the official description above is the record.