Vulnerability in golang-oras-oras-go (UBUNTU-CVE-2026-50151)

Summary

Vulnerability in golang-oras-oras-go (UBUNTU-CVE-2026-50151). Confidential information can be exposed externally. Exploitable via Authorization header.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2026-50151 has been found in golang-oras-oras-go.
Attackers can target a specific entry point like Authorization header over the network to misuse the product.
Confidential information can be exposed externally.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "golang-oras-oras-go UBUNTU-CVE-2026-50151" on the vendor's site.

UBUNTU-CVE-2026-50151 (golang-oras-oras-go)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Authorization header
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in golang-oras-oras-go. Attackers reach the vulnerable code path via Authorization header without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of golang-oras-oras-go. Attack surface: Authorization header.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'golang-oras-oras-go' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'golang-oras-oras-go' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で golang-oras-oras-go を grep し、稼働しているサービス・バージョンを把握する。
2
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Ubuntu:24.04:LTS golang-oras-oras-go

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:26.04:LTS golang-oras-oras-go

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:26.10 golang-oras-oras-go

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

References

report ubuntu.com
report cve.org
report github.com
report github.com