CVE-2025-31484Network attack vector

Unauthorized package uploads via production token injection

Published Apr 2, 2025 · Updated Apr 3, 2025

Improper access control in conda-forge infrastructure from 2025-02-10 through 2025-04-01 allowed remote authenticated users to upload packages. The Azure variable-group configuration assigned the production anaconda.org token to BINSTAR_TOKEN instead of the staging token, granting feedstock jobs direct channel-write authority. Feedstock maintainer access was required; conda-forge found no package uploads that bypassed staging during the exposure window.

CVSS severity9.3
Critical
EPSS probability0.40%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper access control in conda-forge infrastructure from 2025-02-10 through 2025-04-01 allowed remote authenticated users to upload packages. The Azure variable-group configuration assigned the production anaconda.org token to BINSTAR_TOKEN instead of the staging token, granting feedstock jobs direct channel-write authority. Feedstock maintainer access was required; conda-forge found no package uploads that bypassed staging during the exposure window.

The record

CVE
CVE-2025-31484
Published
Apr 2, 2025
Updated
Apr 3, 2025
Vendor
Unknown vendor
Product
Unknown product
Classifications
CWE-284, T1078
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Apr 2, 2025CVE publishedPublication date reported by the CVE source.
  2. Apr 3, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected buildAffected product and version details are unavailable.

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Affected products and versions are unavailable in this record.

Published CVSS scores

9.3GitHub, Inc.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

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-284Improper Access Control
T1078Valid Accounts

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo