Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
Network-reachable blind SSRF (AV:N/AC:L/PR:N) needing the victim to list against a malicious registry (UI:R); pivot to internal services is a scope change (S:C) with only side-channel confidentiality leak (C:L, I:N, A:N).
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
oras-go is a Go library for managing OCI artifacts. Prior to 2.6.2, the parseLink function in registry/remote/utils.go accepts an absolute URL from a registry-controlled Link response header without validating its scheme, host, or port. Tags, Referrers, and Repositories pagination operations then issue a GET request to the attacker-selected URL from the victim's network, allowing blind server-side request forgery against internal services. The response body is not returned to the attacker, but timing and error differences can reveal service reachability, and credentials may be attached when the credential store has an entry for the target host. Exploitation requires a victim to perform a pagination-based listing operation against a malicious registry. The maintainer identifies this report as a duplicate of GHSA-3hr5-mjrr-hfjh and states that remediation is consolidated in that earlier advisory. The consolidated issue is fixed in version 2.6.2.
AnalysisAI
Blind server-side request forgery in the oras-go library lets a malicious or compromised OCI registry steer pagination requests to arbitrary internal endpoints chosen by the attacker. Affected are all oras-go versions prior to 2.6.2; the parseLink routine in registry/remote/utils.go accepted an absolute URL from the registry-supplied Link 'rel=next' header without checking scheme, host, or port, so Tags, Referrers, or Repositories listing calls could be pointed at internal services such as the cloud metadata endpoint 169.254.169.254. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires the victim to run a pagination-based listing operation (Tags, Referrers, or Repositories) using oras-go < 2.6.2 against a registry the attacker controls or has compromised - this is the mandatory UI:R trigger. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | This is a genuine but modest-severity issue. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Upgrade to oras-go 2.6.2 or later, the release in which the same-origin check for Link pagination is enforced (vendor advisory: https://github.com/oras-project/oras-go/security/advisories/GHSA-h7vf-4x9w-h99v; release: https://github.com/oras-project/oras-go/releases/tag/v2.6.2; fix commit: https://github.com/oras-project/oras-go/commit/31da1963f8c327dd089cd29faeae95cf0fc50842). … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-80871