Advisory record · GHSA-vh4v-2xq2-g5cg

ORAS Go forwards registry credentials across registry redirects

CVSS 4.0, no score published

Published by the GitHub Advisory Database at 1 Jul 2026, 21:54 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
oras.land/oras-go/v2Go<2.6.12.6.1
Identifiers
GHSA-vh4v-2xq2-g5cg · GO-2026-5884
Weakness (CWE)
CWE-200 · CWE-522
Published
1 Jul 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

ORAS Go versions before 2.6.1 can forward registry Basic credentials to a different host or port when a registry responds with a redirect or with an upload Location URL. An attacker who controls or can impersonate a registry the client talks to could receive the credentials configured for that registry, including those loaded from a registry config file. Upgrade to oras.land/oras-go/v2 version 2.6.1 or later. The source gives few details on whether the fix covers every redirect path.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
Not published None 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 14:13 UTC First seen by agentprime
  2. 31 Oct 2026, 14:13 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.