oras-go is a Go library for managing OCI artifacts. Prior to 2.6.1, registry/remote/repository.go in blobStore.completePushAfterInitialPost follows a registry-controlled Location header during monolithic blob upload and reuses the Authorization header from the initial POST request for the subsequent PUT request, allowing a malicious registry to return a cross-host Location and receive the caller's credentials at an attacker-controlled endpoint. This issue is fixed in version 2.6.1.
CVE-2026-50151
HIGHPre-NVD 7.57.5—Elevated
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 61% 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
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 38.7%
- KEV
- Not listed
Published
July 1, 2026
Last Modified
July 23, 2026
Advisory Details (4)
Auto-updated Jul 17, 2026🔬 Proof of concept available. Patch available. Sources: github_release, github, github_pr, github_commit.
github_release Patch Available
v2.6.1
Patch available: oras-project/oras-go v2.6.1
https://github.com/oras-project/oras-go/releases/tag/v2.6.1github_commit Patch Available
commit 4683c46ef078 (oras-project/oras-go)
Patch available: oras-project/oras-go v2.6.1 (contains commit 4683c46ef078)
https://github.com/oras-project/oras-go/commit/4683c46ef078091544f5f55fd25102f002806991github_pr Patch Available
fix: validate Location host before blob upload to prevent credential leak
Patch available: oras-project/oras-go v2.6.1 (PR #1152 merged 2026-04-26)
https://github.com/oras-project/oras-go/pull/1152github Patch Available🟡 PoC Available
credential forwarding via unvalidated Location header in oras-go blob upload · Advisory · oras-project/oras-go · GitHub
https://github.com/oras-project/oras-go/security/advisories/GHSA-jxpm-75mh-9fp7Vendor Advisories for CVE-2026-50151(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| oras.land/oras-go/v2 | — | 2.6.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 10× 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-21 15:25 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-01 22:03 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
Frequently asked(5)
What is CVE-2026-50151?
CVE-2026-50151 is a high vulnerability published on July 1, 2026. oras-go is a Go library for managing OCI artifacts. Prior to 2.6.1, registry/remote/repository.go in blobStore.completePushAfterInitialPost follows a registry-controlled Location header during monolithic blob upload and reuses the Authorization header from the initial POST request for the…
When was CVE-2026-50151 disclosed?
CVE-2026-50151 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-50151 actively exploited?
CVE-2026-50151 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 38.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-50151?
CVE-2026-50151 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-50151?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50151, 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-50151
Is Your Infrastructure Affected by CVE-2026-50151?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.