CVE-2026-85732: oras-go: Blind SSRF via unvalidated Link header URL in pagination allows internal network probing
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.
Published Sep 17, 2026
Affected packages
oras.land/oras-go/v2
- Ecosystem
- Go
- Affected
- <= 2.6.1
- Fixed in
- 2.6.2
- Check
go list -m oras.land/oras-go/v2
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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()callsparseLink()for next page URLregistry/remote/repository.go:Referrers()callsparseLink()for next page URLregistry/remote/registry.go:Repositories()callsparseLink()for next page URL
Impact
Blind SSRF from the victim's network. A malicious registry operator can force any oras-go client that lists tags, referrers, or repositories to issue GET requests to arbitrary internal endpoints:
- Cloud instance metadata endpoints for service discovery and IAM role enumeration
- Internal HTTP services for port scanning and triggering side effects
- If the victim's credential store maps credentials for the SSRF target host, those credentials are attached to the request (auth.Client looks up creds by request host)
The attacker cannot read the response body (it's parsed as JSON and fails), making this a blind SSRF. However, timing and error differences can confirm internal service existence.
Attack Chain
- Victim calls
repo.Tags()/repo.Referrers()/registry.Repositories()against attacker-controlled registry - Registry returns a valid first page + malicious Link header pointing to an internal endpoint
parseLink()extracts the absolute URL with zero validation- Pagination loop makes GET request to the internal endpoint from victim's network
PoC
Expand PoC
// Malicious registry handler for /v2/repo/tags/list:
func handler(w http.ResponseWriter, r *http.Request) {
// Link header points to cloud metadata or internal service
w.Header().Set("Link", `<http://internal-service:8080/admin>; rel="next"`)
w.Header().Set("Content-Type", "application/json")
json.NewEncoder(w).Encode(map[string][]string{"tags": {"v1"}})
}
// Victim code:
repo, _ := remote.NewRepository("attacker-registry.io/repo")
repo.Tags(ctx, "", func(tags []string) error { return nil })
// Result: GET http://internal-service:8080/admin is made from victim's networkSuggested Fix
Validate that the URL returned by parseLink() has the same host and scheme as the original request before using it for the next pagination request. Reject cross-host or scheme-downgrade URLs.
Reported by zx (Jace)
Credited to manus-use.
References
- https://github.com/oras-project/oras-go/security/advisories/GHSA-h7vf-4x9w-h99v
- https://nvd.nist.gov/vuln/detail/CVE-2026-85732
- https://github.com/oras-project/oras-go/commit/31da1963f8c327dd089cd29faeae95cf0fc50842
- https://github.com/oras-project/oras-go/releases/tag/v2.6.2
- https://github.com/advisories/GHSA-h7vf-4x9w-h99v
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-85731
oras-go: Arbitrary file write outside file.Store root via symlink-chain bypass in tar extraction (pushDir)
high8.8Sep 17, 2026CVE-2026-48978
oras-go: Malicious registry can hijack Bearer token realm to exfiltrate credentials and refresh tokens
low2.1No fixJul 1, 2026CVE-2026-50151
oras-go blob upload vulnerable to credential forwarding via unvalidated Location header
high7.5Jul 1, 2026CVE-2026-50162
oras-go has file store write outside workingDir via symlink traversal
medium6.9Jul 1, 2026CVE-2026-50163
`oras-go` tar extraction: Hardlink entry with relative Linkname escapes extract dir via process CWD resolution
high7.1Jul 1, 2026GHSA-vh4v-2xq2-g5cg
ORAS Go forwards registry credentials across registry redirects
medium6.9Jul 1, 2026
