CVE-2026-50151 is a high-severity (CVSS 7.5) Server-Side Request Forgery (SSRF) vulnerability in oras.land/oras-go/v2. A fix is available for oras.land/oras-go/v2 — see the affected versions and patch details below.
oras-go: credential forwarding via unvalidated Location header in blob upload
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-50151.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-50151 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 389,824 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
oras.land/oras-go/v2Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
oras-go follows a registry-controlled Location header during the monolithic blob upload flow and reuses the Authorization header from the initial POST request for the subsequent PUT request. If a malicious registry returns a cross-host Location, oras-go can send the caller's credentials to an attacker-controlled endpoint.
Affected Versions
tested: v2.6.0 (commit 03243809936cce826494b5506f724c6dc11115b1, as-of 2026-01-24) range: unknown; likely affects earlier v2.x releases that include the same upload flow
Impact
Credential leak to an attacker-controlled endpoint and client-side ssrf to a cross-host target.
Affected Component
registry/remote/repository.go:878-916(blobStore.completePushAfterInitialPost)
Reproduction
Attachments include poc.zip with a local-only harness (no real registry required). It runs a fake registry server that returns a cross-host Location and a second server that records whether it received Authorization.
unzip -q -o poc.zip -d /tmp/poc
cd /tmp/poc/poc-F-ORAS-LOCATION-UPLOAD-001
make canonical
make control
Recommended Fix
- validate
Locationbefore uploading (scheme + hostname + effective port) against the original request, or require an explicit opt-in allowlist for cross-host upload urls - never forward
Authorizationwhen the upload target changes host or scheme
references
- security policy: https://github.com/oras-project/oras-go/security/policy
- vulnerable code:
registry/remote/repository.go(seeblobStore.completePushAfterInitialPost)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | oras.land/oras-go/v2 | all versions | 2.6.1go get oras.land/oras-go/v2@v2.6.1 |
Affected Products
oraslinuxfoundationDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for oras.land/oras-go/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update oras.land/oras-go/v2 to 2.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-50151 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
A flaw was found in oras-go. During monolithic blob upload, the Authorization header is reused for cross-host Location redirects, allowing a malicious registry to exfiltrate caller credentials.
Upgrade to oras-go v2.6.1 or later.Source: Red Hat security advisory for CVE-2026-50151 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Multicluster Global Hub 1.4.9 | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1788375682 | RHSA-2026:67516 |
| Multicluster Global Hub 1.5.8 | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1789515639 | RHSA-2026:71597 |
| Multicluster Global Hub 1.6.6 | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1790086248 | RHSA-2026:73419 |
| Multicluster Global Hub 1.7.3 | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1788376193 | RHSA-2026:67842 |
| Multicluster Global Hub 1.8.2 | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1788441983 | RHSA-2026:68515 |
| Multicluster Global Hub 1.8.2 | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1790639009 | RHSA-2026:73038 |
| Red Hat Advanced Cluster Management for Kubernetes 2.13 | rhacm2/multicloud-integrations-rhel9:1784652040 | RHSA-2026:47737 |
Frequently Asked Questions
Is CVE-2026-50151 in your dependencies?
Find it across Go, including transitive dependencies.