{
  "affected": [
    {
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "70f3f09e64968d5f0a7b0525846f17cad42dd052"
            }
          ],
          "repo": "https://github.com/conda-forge/infrastructure",
          "type": "GIT"
        }
      ]
    }
  ],
  "aliases": [
    "GHSA-m4h2-49xf-vq72"
  ],
  "database_specific": {
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
      "CWE-284"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/31xxx/CVE-2025-31484.json"
  },
  "details": "conda-forge infrastructure holds common configurations and settings for key pieces of the conda-forge infrastructure.\nBetween 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.",
  "id": "CVE-2025-31484",
  "modified": "2026-04-01T23:08:43.743941789Z",
  "published": "2025-04-02T21:38:03.493Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/31xxx/CVE-2025-31484.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/conda-forge/infrastructure/security/advisories/GHSA-m4h2-49xf-vq72"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-31484"
    },
    {
      "type": "FIX",
      "url": "https://github.com/conda-forge/infrastructure/commit/70f3f09e64968d5f0a7b0525846f17cad42dd052"
    }
  ],
  "schema_version": "1.7.3",
  "severity": [
    {
      "score": "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",
      "type": "CVSS_V4"
    }
  ],
  "summary": "conda-forge infrastructure uses a bad token for Azure's cf-staging access"
}