CVE-2026-85732: oras-go: Blind SSRF via unvalidated Link header URL in pagination allows internal network probing
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.38% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: oras-project oras-go 2.6.2.
Low priority for now. Upgrade to oras-project oras-go 2.6.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- EPSS
- 0.3% · 32th percentile
- CWE
- CWE-918
Report tools
Action score
18
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 4.7
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
oras-project oras-go
- < 2.6.2affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | golang-oras-oras-go | from 0 | — |
| Debian:14 | golang-oras-oras-go | before 2.6.2-1 | 2.6.2-1 |
| Go | oras.land/oras-go/v2 | before 2.6.2 | 2.6.2 |
| openSUSE:Leap 16.0 | helm | before 4.3.0-160000.1.1 | 4.3.0-160000.1.1 |
| openSUSE:Leap 16.0 | helm | before 4.3.0-160000.2.1 | 4.3.0-160000.2.1 |
| openSUSE:Tumbleweed | helm | before 4.3.0-2.1 | 4.3.0-2.1 |
| openSUSE:Tumbleweed | helm3 | before 3.22.0-1.1 | 3.22.0-1.1 |
| SUSE:Linux Enterprise Micro 5.5 | helm | before 3.22.0-150000.1.99.1 | 3.22.0-150000.1.99.1 |
| SUSE:Linux Enterprise Micro 5.5 | helm | before 3.22.1-150000.1.104.1 | 3.22.1-150000.1.104.1 |
| SUSE:Linux Micro 6.1 | helm | before 4.3.0-slfo.1.1_1.1 | 4.3.0-slfo.1.1_1.1 |
| SUSE:Linux Micro 6.2 | helm | before 4.3.0-160000.2.1 | 4.3.0-160000.2.1 |
| SUSE:Linux Micro 6.2 | helm | before 4.3.0-160000.1.1 | 4.3.0-160000.1.1 |
Same product
oras-project: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-85731oras-go: Arbitrary file write outside file.Store root via symlink-chain bypass in tar extraction (pushDir)35Monitor
- CVE-2026-50163oras-go: Hardlink entry with relative Linkname escapes extract dir via process CWD resolution in `oras-go` tar extraction28Monitor
- CVE-2026-50162oras-go: file store write outside workingDir via symlink traversal27Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-48978Jul 17, 2026 · oras-go: Malicious registry can hijack Bearer token realm to exfiltrate credentials and refresh tokens8Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| oras-project oras-go | 2.6.2 · description | Vendor (CNA) |
| debian:golang-oras-oras-go | 2.6.2-1 · Debian:14 | Package registry (OSV) |
| Go:oras.land/oras-go/v2 | 2.6.2 | Package registry (OSV) |
| opensuse:helm | 4.3.0-2.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:helm3 | 3.22.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:helm | 3.22.0-150000.1.99.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:helm | 4.3.0-160000.1.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.