oras-go: Blind SSRF via unvalidated Link header URL in pagination allows internal network probing
CVE-2026-85732GHSA-h7vf-4x9w-h99v
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (oras.land/oras-go/v2 2.6.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- <= 2.6.1
- Fixed in
- 2.6.2
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-h7vf-4x9w-h99v lists affected ranges: Go oras.land/oras-go/v2 >=0 <2.6.2 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GO-2026-6497 lists affected ranges: Go oras.land/oras-go/v2 >=0 <2.6.2 (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-h7vf-4x9w-h99v lists affected ranges: Go oras.land/oras-go/v2 >=0 <=2.6.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 4.7 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
- EPSS
- CVE-2026-85732: 0.38% estimated exploitation activity in the next 30 days; percentile 32.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary oras-go's pagination helper parseLink() in registry/remote/utils.go follows the Link response header from a registry without validating the URL's host or scheme. When a malicious registry returns a Link header containing an absolute URL pointing to an arbitrary host (e.g., a cloud metadata endpoint), the client makes GET requests to that host from the victim's network. This affects all pagination-based listing operations: Tags, Referrers, and Repositories (catalog). Root Cause parseLink() at registry/remote/utils.go:54 calls resp.Request.URL.Parse(link) which, for absolute URLs, returns the absolute URL unchanged. The result is passed directly to the next pagination loop iteration where http.NewRequestWithContext() creates a GET request to the attacker-specified URL. No host comparison, scheme validation, or IP filtering exists between parseLink output and the HTTP request. Affected Code Paths - registry/remote/repository.go:Tags() calls parseLink() for next page URL -…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-h7vf-4x9w-h99v
- Revision 2 · amended ·
Amended from osv record GO-2026-6497
- Revision 1 · created ·
Published from osv record GHSA-h7vf-4x9w-h99v
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-85732 Advisory: oras-go: Blind SSRF via unvalidated Link header URL in pagination allows internal network probing IDs: CVE-2026-85732, GHSA-h7vf-4x9w-h99v Record: https://patchnext.com/advisories/cve-2026-85732 (revision 3, source checked 26 Oct 2026, 15:29 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 4.7) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: oras.land/oras-go/v2 2.6.2. A vendor fix does not mean a deployment is fixed. ## Affected components - Go oras.land/oras-go/v2: affected <= 2.6.1; fixed in 2.6.2 ## Suggested inspection (read-only) - Go oras.land/oras-go/v2: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on oras.land/oras-go/v2. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-h7vf-4x9w-h99v (OSV record GHSA-h7vf-4x9w-h99v lists affected ranges: Go oras.land/oras-go/v2 >=0 <2.6.2 (fixed)) - Verified: https://osv.dev/vulnerability/GO-2026-6497 (OSV record GO-2026-6497 lists affected ranges: Go oras.land/oras-go/v2 >=0 <2.6.2 (fixed)) - Verified: https://github.com/advisories/GHSA-h7vf-4x9w-h99v (GitHub-reviewed advisory GHSA-h7vf-4x9w-h99v lists affected ranges: Go oras.land/oras-go/v2 >=0 <=2.6.1) Commands are suggestions: review each one before running it.
Loading voting…