oras-go blob upload vulnerable to credential forwarding via unvalidated Location header

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-50151: 0.38% estimated exploitation activity in the next 30 days; percentile 32.29 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. Recommended Fix - validate Location before…

Published by the source

1 Jul 2026, 21:35 UTC

Last modified by the source

1 Jul 2026, 21:35 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jxpm-75mh-9fp7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-50151

Advisory: oras-go blob upload vulnerable to credential forwarding via unvalidated Location header
IDs: CVE-2026-50151, GHSA-jxpm-75mh-9fp7
Record: https://patchnext.com/advisories/cve-2026-50151 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: oras.land/oras-go/v2 2.6.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go oras.land/oras-go/v2: affected < 2.6.1; fixed in 2.6.1

## Suggested inspection (read-only)
- Go oras.land/oras-go/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on oras.land/oras-go/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jxpm-75mh-9fp7 (GitHub-reviewed advisory GHSA-jxpm-75mh-9fp7 lists affected ranges: Go oras.land/oras-go/v2 >=0 <2.6.1)

Commands are suggestions: review each one before running it.