VDB

GO-2025-3460

GO-2025-3460 PUBLISHED

Record from OSV · Published March 3, 2025

Distribution's token authentication allows attacker to inject an untrusted signing key in a JWT in github.com/distribution/distribution

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kotsChainguard1.124.3-r1
zotChainguard2.1.2-r2
harbor-fips-2.12Chainguard2.12.4-r41
harbor-2.12Chainguard2.12.4-r43
kotsWolfi1.124.3-r1
zotWolfi2.1.2-r2

Affected products

VendorProductVersions
chainguardharbor-fips-2.13*
chainguardkots0
chainguardzot0
github.comdistribution/distribution0
chainguardharbor-fips-2.120
chainguardharbor-fips-2.15*
chainguardharbor-2.15*
wolfiharbor-2.14*
chainguardharbor-2.120
chainguardharbor-2.14*
wolfikots0
chainguardharbor-2.13*
wolfizot0
chainguardharbor-fips-2.14*

Timeline

  • Mar 3, 2025 CVE Published
  • Feb 4, 2026 CVE Updated
  • May 18, 2026 Security Advisory

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln GO-2025-3460
vulnetix vdb fixes GO-2025-3460

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/GO-2025-3460/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›