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.
CVE-2026-48978
LOWPre-NVD 2.12.1—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
2.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 2.1Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 2.1
- EG Score
- 2.1(medium)
- EG Risk
- 10(Track)EG Risk 10/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity21% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 17.7%
- KEV
- Not listed
Published
July 1, 2026
Last Modified
July 23, 2026
References (3)
- security-advisories@githubhttps://github.com/oras-project/oras-go/commit/7a9f4b0b9558821b0422152ebe21ae56930fe764
- security-advisories@githubhttps://github.com/oras-project/oras-go/releases/tag/v2.6.1
- security-advisories@githubhttps://github.com/oras-project/oras-go/security/advisories/GHSA-xf85-363p-868w
Vendor Advisories for CVE-2026-48978(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 1 ecosystem)
Go(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| oras.land/oras-go | — | — | — |
| oras.land/oras-go/v2 | — | 2.6.1 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:18 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 03:52 UTCEG score recompute
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-17 19:50 UTCEG score recompute▲ 2.10
- 2026-07-17 19:49 UTCMITRE cvelistV5CVSS v3 → 2.1 · CVSS v4 → 2.1
- 2026-07-01 22:03 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-918 · CWE-319
Frequently asked(5)
What is CVE-2026-48978?
CVE-2026-48978 is a low vulnerability published on July 1, 2026. 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…
When was CVE-2026-48978 disclosed?
CVE-2026-48978 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48978 actively exploited?
CVE-2026-48978 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48978?
CVE-2026-48978 has a CVSS v3 base score of 2.1 (NVD).
How do I remediate CVE-2026-48978?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48978, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48978
Is Your Infrastructure Affected by CVE-2026-48978?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.