CVE-2025-24976Network attack vector

Authentication bypass via untrusted JWT signing key

Published Feb 11, 2025 · Updated Jan 23, 2026

Authentication bypass in CNCF Distribution 3.0.0-beta.1 through 3.0.0-rc.2 allows remote attackers to forge registry access tokens. The registry/auth/token verifyJWK path accepts JWK key material from a token when its kid matches a trusted key ID, then verifies the signature with that untrusted key. Token authentication must be enabled; forged claims can grant registry operations permitted by the impersonated token.

CVSS severityUnavailable
Unscored
EPSS probability0.35%
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

Authentication bypass in CNCF Distribution 3.0.0-beta.1 through 3.0.0-rc.2 allows remote attackers to forge registry access tokens. The registry/auth/token verifyJWK path accepts JWK key material from a token when its kid matches a trusted key ID, then verifies the signature with that untrusted key. Token authentication must be enabled; forged claims can grant registry operations permitted by the impersonated token.

The record

CVE
CVE-2025-24976
Published
Feb 11, 2025
Updated
Jan 23, 2026
Vendor
CNCF Distribution
Product
Distribution
Classifications
CWE-639, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Feb 11, 2025CVE publishedPublication date reported by the CVE source.
  2. Jan 23, 2026Record 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?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 3.0.0-beta.1, <= 3.0.0-rc.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

CNCF Distribution · Distributionversion=>= 3.0.0-beta.1, <= 3.0.0-rc.2

Published CVSS scores

6.6GitHub, Inc.CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U

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 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-639Authorization Bypass Through User-Controlled Key
T1190Exploit Public-Facing Application

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