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.
Affected products
linuxfoundation: oras
References5
- github.com/oras-project/oras-go/security/advisories/GHSA-jxpm-7… ExploitMitigationVendor Advisory
- github.com/oras-project/oras-go/security/advisories/GHSA-jxpm-7… ExploitMitigationVendor Advisory
- github.com/oras-project/oras-go/commit/4683c46ef078091544f5f55f… Patch
- github.com/oras-project/oras-go/pull/1152 Issue TrackingPatch
- github.com/oras-project/oras-go/releases/tag/v2.6.1 Release Notes
Metrics
- CVSS 3.1
-
7.5
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - EPSS — exploit probability
- 0% percentile: 33 · as of 14 November 2026
- CWE
- CWE-918
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.