Skip to content
Fencer Intel
medium 4.7

CVE-2026-85732 json

oras-go: Blind SSRF via unvalidated Link header URL in pagination allows internal network probing

published last mo. modified last mo. also EUVD-2026-80871 , GHSA-h7vf-4x9w-h99v , GO-2026-6497

cvss
4.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 32%
public exploits
0
none known

Summary

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.

Patch / fix

  • go oras.land/oras-go/v2 2.6.2
  • linuxfoundation oras 2.6.2
  • golang-oras-oras-go Debian 14 2.6.2-1

debian advisories DEBIAN-CVE-2026-85732

  • helm SLES for SAP 15 SP6, SLES for SAP 15 SP5, SLES for SAP 15 SP4 +10 more 3.22.1-150000.1.104.1
  • helm Linux Micro 6.1 4.3.0-slfo.1.1_1.1
  • helm SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 4.3.0-160000.2.1
  • helm SLES for SAP 15 SP6, SLES for SAP 15 SP5, SLES for SAP 15 SP4 +10 more 3.22.0-150000.1.99.1
  • helm SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 4.3.0-160000.1.1

suse advisories SUSE-SU-2026:5119-1SUSE-SU-2026:24282-1SUSE-SU-2026:24120-1SUSE-SU-2026:24247-1SUSE-SU-2026:4417-1SUSE-SU-2026:23973-1

  • helm openSUSE Leap 16.0 4.3.0-160000.2.1
  • helm openSUSE Leap 16.0 4.3.0-160000.1.1
  • helm openSUSE Tumbleweed 4.3.0-2.1
  • helm3 openSUSE Tumbleweed 3.22.0-1.1

opensuse advisories openSUSE-SU-2026:22057-1openSUSE-SU-2026:21983-1openSUSE-SU-2026:11848-1openSUSE-SU-2026:11832-1

Is CVE-2026-85732 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-85732 updated cvss 4.7

github.com/oras-project/oras-go: oras-go: Blind Server-Side Request Forgery via unvalidated Link header URL

  • Red Hat OpenShift AI (RHOAI) rhoai/odh-ai-gateway-operator-rhel9, rhoai/odh-ogx-module-operator-rhel9, rhoai/odh-kserve-module-operator-rhel9
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last mo.

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • github.com https://github.com/oras-project/oras-go/security/advisories/GHSA-h7vf-4x9w-h99v referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 4.7 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
GitHub 3.1 4.7 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
go oras.land/oras-go/v2
<2.6.2
2.6.2

Affected products

  • oras-project oras-go

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.