CVE-2026-48978: CWE-918: Server-Side Request Forgery (SSRF) in oras-project oras-go
oras-go is a Go library for managing OCI artifacts. Prior to 2.6.1, auth.Client follows the realm URL from a registry's WWW-Authenticate: Bearer challenge without validating the scheme or host, allowing a malicious or compromised registry to cause SSRF to internal networks such as http://169.254.169.254/, http://10.0.0.x/, and http://127.0.0.1/, or to downgrade a registry contacted over https:// to an http:// token endpoint in registry/remote/auth/client.go through Client.Do(), Client.fetchBearerToken(), fetchDistributionToken, and fetchOAuth2Token. This issue is fixed in version 2.6.1.
AI Analysis
Technical Summary
The oras-go Go library for managing OCI artifacts contains an SSRF vulnerability (CWE-918) in its auth.Client implementation. Before version 2.6.1, the client blindly follows the realm URL provided in a registry's WWW-Authenticate Bearer challenge without validating the URL scheme or host. This flaw enables attackers controlling or compromising a registry to trigger SSRF requests to internal IP addresses such as 169.254.169.254, 10.0.0.x, and 127.0.0.1, or to downgrade secure HTTPS token endpoints to HTTP. The vulnerable code paths include Client.Do(), Client.fetchBearerToken(), fetchDistributionToken, and fetchOAuth2Token in registry/remote/auth/client.go. The vulnerability is resolved in version 2.6.1.
Potential Impact
An attacker controlling or compromising a registry can exploit this vulnerability to perform SSRF attacks, potentially accessing internal network resources that are normally inaccessible externally. The downgrade from HTTPS to HTTP token endpoints could also expose token exchanges to interception. However, the CVSS score is low (2.1), indicating limited impact or exploitability under typical conditions.
Mitigation Recommendations
Upgrade to oras-go version 2.6.1 or later where this SSRF vulnerability is fixed. No other official remediation or temporary fixes are documented. Patch status is confirmed by the vendor stating the issue is fixed in 2.6.1.
CVE-2026-48978: CWE-918: Server-Side Request Forgery (SSRF) in oras-project oras-go
Description
oras-go is a Go library for managing OCI artifacts. Prior to 2.6.1, auth.Client follows the realm URL from a registry's WWW-Authenticate: Bearer challenge without validating the scheme or host, allowing a malicious or compromised registry to cause SSRF to internal networks such as http://169.254.169.254/, http://10.0.0.x/, and http://127.0.0.1/, or to downgrade a registry contacted over https:// to an http:// token endpoint in registry/remote/auth/client.go through Client.Do(), Client.fetchBearerToken(), fetchDistributionToken, and fetchOAuth2Token. This issue is fixed in version 2.6.1.
CVSS v4.0
Score 2.1low
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The oras-go Go library for managing OCI artifacts contains an SSRF vulnerability (CWE-918) in its auth.Client implementation. Before version 2.6.1, the client blindly follows the realm URL provided in a registry's WWW-Authenticate Bearer challenge without validating the URL scheme or host. This flaw enables attackers controlling or compromising a registry to trigger SSRF requests to internal IP addresses such as 169.254.169.254, 10.0.0.x, and 127.0.0.1, or to downgrade secure HTTPS token endpoints to HTTP. The vulnerable code paths include Client.Do(), Client.fetchBearerToken(), fetchDistributionToken, and fetchOAuth2Token in registry/remote/auth/client.go. The vulnerability is resolved in version 2.6.1.
Potential Impact
An attacker controlling or compromising a registry can exploit this vulnerability to perform SSRF attacks, potentially accessing internal network resources that are normally inaccessible externally. The downgrade from HTTPS to HTTP token endpoints could also expose token exchanges to interception. However, the CVSS score is low (2.1), indicating limited impact or exploitability under typical conditions.
Mitigation Recommendations
Upgrade to oras-go version 2.6.1 or later where this SSRF vulnerability is fixed. No other official remediation or temporary fixes are documented. Patch status is confirmed by the vendor stating the issue is fixed in 2.6.1.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-26T23:26:07.974Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5b5eae2d1edb114c7fb324
Added to database: 07/18/2026, 11:08:30 UTC
Last enriched: 07/18/2026, 11:53:50 UTC
Last updated: 07/18/2026, 13:13:14 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.