CVE-2026-50151

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% 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
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

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 computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

July 1, 2026

Last Modified

August 26, 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.1
github_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/4683c46ef078091544f5f55fd25102f002806991
github_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/1152
github 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-9fp7

Vendor Advisories for CVE-2026-50151(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhacm2/multicluster-operators-subscription-rhel9:17847401432026-07-29redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-oras-oras-go2.5.0-1, 2.6.0-1, 2.6.2-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-oras-oras-go2.5.0-1, 2.6.0-12.6.2-1—
Go(1)
PackageVulnerable rangeFixed inDependents
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 12× in last 7d / 57× 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.

Showing the most recent 100 of 156 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 06:28 UTCEG score recompute
  3. 2026-09-18 06:28 UTCVendor advisory
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-14 00:21 UTCEG score recompute
  7. 2026-09-14 00:21 UTCVendor advisory
  8. 2026-09-13 16:47 UTCEPSS rescore
  9. 2026-09-13 09:07 UTCEG score recompute
  10. 2026-09-13 09:07 UTCVendor advisory
  11. 2026-09-12 14:36 UTCEG score recompute
  12. 2026-09-12 14:36 UTCVendor advisory
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-10 09:35 UTCEPSS rescore
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-07 16:01 UTCEPSS rescore
  17. 2026-09-06 14:26 UTCEG score recompute
  18. 2026-09-06 14:26 UTCVendor advisory
  19. 2026-09-06 13:47 UTCEPSS rescore
  20. 2026-09-06 00:37 UTCEG score recompute
  21. 2026-09-06 00:37 UTCVendor advisory
  22. 2026-09-04 05:06 UTCEPSS rescore
  23. 2026-09-02 14:12 UTCEPSS rescore
  24. 2026-09-01 13:54 UTCEPSS rescore
  25. 2026-08-31 00:19 UTCEG score recompute
Show 75 more
  1. 2026-08-31 00:19 UTCVendor advisory
  2. 2026-08-30 19:17 UTCEPSS rescore
  3. 2026-08-30 11:35 UTCEG score recompute
  4. 2026-08-30 11:35 UTCVendor advisory
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 22:24 UTCEG score recompute
  8. 2026-08-27 22:24 UTCVendor advisory
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-26 19:42 UTCEG score recompute
  11. 2026-08-26 19:42 UTCVendor advisory
  12. 2026-08-26 14:46 UTCEPSS rescore
  13. 2026-08-25 16:15 UTCEG score recompute
  14. 2026-08-25 16:15 UTCVendor advisory
  15. 2026-08-25 13:49 UTCEPSS rescore
  16. 2026-08-24 23:34 UTCEG score recompute
  17. 2026-08-24 23:34 UTCVendor advisory
  18. 2026-08-24 10:49 UTCEG score recompute
  19. 2026-08-24 10:49 UTCVendor advisory
  20. 2026-08-23 21:55 UTCVendor advisory
  21. 2026-08-23 09:09 UTCEG score recompute
  22. 2026-08-23 09:09 UTCVendor advisory
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-22 20:24 UTCVendor advisory
  25. 2026-08-22 07:39 UTCEG score recompute
  26. 2026-08-22 07:39 UTCVendor advisory
  27. 2026-08-21 23:49 UTCEPSS rescore
  28. 2026-08-21 18:54 UTCVendor advisory
  29. 2026-08-21 06:09 UTCEG score recompute
  30. 2026-08-21 06:09 UTCVendor advisory
  31. 2026-08-20 22:55 UTCEPSS rescore
  32. 2026-08-20 17:23 UTCVendor advisory
  33. 2026-08-20 04:36 UTCEG score recompute
  34. 2026-08-20 04:36 UTCVendor advisory
  35. 2026-08-19 17:04 UTCEPSS rescore
  36. 2026-08-19 09:53 UTCVendor advisory
  37. 2026-08-18 20:57 UTCEG score recompute
  38. 2026-08-18 20:57 UTCVendor advisory
  39. 2026-08-18 13:48 UTCEPSS rescore
  40. 2026-08-18 06:20 UTCVendor advisory
  41. 2026-08-17 16:50 UTCEG score recompute
  42. 2026-08-17 16:50 UTCVendor advisory
  43. 2026-08-17 13:47 UTCEPSS rescore
  44. 2026-08-17 04:06 UTCVendor advisory
  45. 2026-08-16 15:21 UTCEG score recompute
  46. 2026-08-16 15:21 UTCVendor advisory
  47. 2026-08-16 14:56 UTCEPSS rescore
  48. 2026-08-16 02:36 UTCEG score recompute
  49. 2026-08-16 02:36 UTCVendor advisory
  50. 2026-08-16 02:14 UTCEPSS rescore
  51. 2026-08-15 13:52 UTCEG score recompute
  52. 2026-08-15 13:52 UTCVendor advisory
  53. 2026-08-15 01:30 UTCEPSS rescore
  54. 2026-08-15 01:07 UTCVendor advisory
  55. 2026-08-14 12:23 UTCVendor advisory
  56. 2026-08-13 23:38 UTCEG score recompute
  57. 2026-08-13 23:38 UTCVendor advisory
  58. 2026-08-13 22:00 UTCEPSS rescore
  59. 2026-08-13 10:53 UTCVendor advisory
  60. 2026-08-12 22:08 UTCEG score recompute
  61. 2026-08-12 22:08 UTCVendor advisory
  62. 2026-08-12 13:51 UTCEPSS rescore
  63. 2026-08-12 09:24 UTCVendor advisory
  64. 2026-08-11 20:39 UTCEG score recompute
  65. 2026-08-11 20:39 UTCVendor advisory
  66. 2026-08-11 07:54 UTCEG score recompute
  67. 2026-08-11 07:54 UTCVendor advisory
  68. 2026-08-11 00:00 UTCEPSS rescore
  69. 2026-08-10 19:10 UTCVendor advisory
  70. 2026-08-10 06:25 UTCVendor advisory
  71. 2026-08-09 17:40 UTCEG score recompute
  72. 2026-08-09 17:40 UTCVendor advisory
  73. 2026-08-09 13:46 UTCEPSS rescore
  74. 2026-08-09 04:56 UTCEG score recompute
  75. 2026-08-09 04:56 UTCVendor advisory

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 August 26, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 67.9% of all scored CVEs.
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

Explore →

Is Your Infrastructure Affected by CVE-2026-50151?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs