# ORAS Go forwards registry credentials across registry redirects

Advisory record · `GHSA-vh4v-2xq2-g5cg`

- **Identifiers:** `GHSA-vh4v-2xq2-g5cg` · `GO-2026-5884`
- **State:** Confirmed
- **Severity:** CVSS 4.0, no score published
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-522](https://cwe.mitre.org/data/definitions/522.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md)
- **Published:** 1 Jul 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `oras.land/oras-go/v2` (Go): affected `<2.6.1`; fixed in `2.6.1`

## 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

- Score not published, CVSS 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`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:13 UTC: First seen by agentprime
- 31 Oct 2026, 14:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-vh4v-2xq2-g5cg)

## Sources

- [GitHub Advisory Database: GHSA-vh4v-2xq2-g5cg](https://github.com/advisories/GHSA-vh4v-2xq2-g5cg)
- [OSV: GHSA-vh4v-2xq2-g5cg](https://osv.dev/vulnerability/GHSA-vh4v-2xq2-g5cg)
- <https://github.com/oras-project/oras-go/security/advisories/GHSA-vh4v-2xq2-g5cg>
- <https://github.com/oras-project/oras-go/commit/3c2e884e12ea52b6bff60c97f1edb7df7d0e0909>
- <https://github.com/oras-project/oras-go>
- <https://github.com/oras-project/oras-go/releases/tag/v2.6.1>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-vh4v-2xq2-g5cg>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-vh4v-2xq2-g5cg/>. Everything for agents: <https://agentprime.io/llms.txt>.