CVE-2026-85732VulnerabilityPublished 16 Sep 2026Updated 28 Oct 2026

Golang oras oras go: Prior to 2.6.2, the parseLink function in registry/remote/utils.go accepts an absolute URL from a

Affects golang-oras-oras-goSource GCVE Database

Authoritative record:CVE-2026-85732· Medium 4.7

Not known to be exploited · CVSS 4.7 Medium · fixed in 2.6.2 : update golang-oras-oras-go when convenient.

Data as of 29 Oct 2026, 01:31 UTC

CVSS 3.1 base score

4.7Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 2.6.2

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSgolang-oras-oras-go`pkg:deb/ubuntu/golang-oras-oras-go?arch=source&distro=resolute`Other threats	Affected =2.5.0-1 =2.6.0-1	Fixed in–
Ubuntu 24.04 LTSgolang-oras-oras-go`pkg:deb/ubuntu/golang-oras-oras-go?arch=source&distro=noble`Other threats	Affected =1.1.1-1ubuntu1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Golang oras-go version 2.6.2 or later, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory. Users should avoid interacting with untrusted registries until patched.

Description

A vulnerability in the Golang oras-go library prior to version 2.6.2 allows server-side request forgery (SSRF) via the parseLink function. This function accepts an absolute URL from a registry-controlled Link response header without validating its scheme, host, or port. An attacker can exploit this by causing a victim to perform pagination operations against a malicious registry, leading to blind SSRF against internal services. The vulnerability is fixed in version 2.6.2.

Impact

This vulnerability enables blind server-side request forgery (SSRF) from the victim's network to attacker-controlled URLs, potentially allowing attackers to probe internal services and network reachability. Credentials stored for targeted hosts may be sent with the forged requests, increasing the risk of unauthorized access. The response body is not exposed to the attacker, limiting direct data exfiltration. Exploitation requires user interaction with a malicious registry during pagination operations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 01:31 UTC

Technical details

References

Community reviews

Related threats