CVE-2026-50151: oras-go is a Go library for managing OCI artifacts

Q: How do I fix CVE-2026-50151?

oras: upgrade to 2.6.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-50151 being exploited?

CVE-2026-50151 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-50151 affect?

CVE-2026-50151 affects oras. Severity is high (CVSS 7.5). 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 Authoriza

Q: How urgent is CVE-2026-50151?

Priority 49/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

This week

HIGH 7.5REMOTEWATCHLISTUPGRADE

CVE-2026-50151 is a high-severity flaw (CVSS 7.5) affecting oras. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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. T

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 69%)
CISA exploited list	No
Weakness	CWE-918
Published	2026-07-17
Last modified	2026-10-24

Publisher (CNA): GitHub, Inc. · Vendor: linuxfoundation

Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-07-17 20:17 UTCPublished CVE record published
2026-10-24 20:10 UTCUpdated Record last modified

linuxfoundation oras UPGRADE

Affected: < 2.6.1

Fixed in: 2.6.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy oras || rpm -q oras || oras --version

2. UPGRADE to 2.6.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade oras

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade oras

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-50151?

oras: upgrade to 2.6.1. Exact commands for each OS are on this page.

Is CVE-2026-50151 being exploited?

CVE-2026-50151 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-50151 affect?

CVE-2026-50151 affects oras. Severity is high (CVSS 7.5). 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 Authoriza

How urgent is CVE-2026-50151?

Priority 49/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

References

← Back to latest CVEs