Server-Side Request Forgery (SSRF) Affecting manifest-tool package, versions <2.2.2-r16
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-WOLFILATEST-MANIFESTTOOL-19964075
- published20 Sept 2026
- disclosed16 Sept 2026
Introduced: 16 Sep 2026
NewCVE-2026-85732 (opens in a new tab)How to fix?
Upgrade Wolfi manifest-tool to version 2.2.2-r16 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream manifest-tool package and not the manifest-tool package as distributed by Wolfi.
See How to fix? for Wolfi relevant fixed versions and status.
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.