7.5
HIGH CVSS 3.1
CVE-2026-50151
oras-go: credential forwarding via unvalidated Location header in blob upload
Description

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.

INFO

Published Date :

July 17, 2026, 8:17 p.m.

Last Modified :

July 17, 2026, 8:17 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-50151 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 HIGH [email protected]
Solution
Update oras-go to version 2.6.1 to fix credential exposure via malicious registry redirects.
  • Update oras-go to version 2.6.1.
  • Ensure registry communication uses authenticated, secure channels.
References to Advisories, Solutions, and Tools
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-50151 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-50151 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-50151 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-50151 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Jul. 17, 2026

    Action Type Old Value New Value
    Added Affected [{'vendor': 'oras-project', 'product': 'oras-go', 'versions': [{'status': 'affected', 'version': '< 2.6.1'}]}]
    Added Description 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.
    Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
    Added CWE CWE-918
    Added Reference https://github.com/oras-project/oras-go/commit/4683c46ef078091544f5f55fd25102f002806991
    Added Reference https://github.com/oras-project/oras-go/pull/1152
    Added Reference https://github.com/oras-project/oras-go/releases/tag/v2.6.1
    Added Reference https://github.com/oras-project/oras-go/security/advisories/GHSA-jxpm-75mh-9fp7
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.