Categories
CVE-2026-50151 high CVSS 7.5

SSRF (Server-Side Request Forgery) in oras.land/oras-go/v2 (CVE-2026-50151)

Summary

SSRF in oras.land/oras-go/v2 (CVE-2026-50151). Confidential information can be exposed externally. Mitigation: upgrade to 2.6.1 or later.

Original description

The description as published by the source.

Oras-go: Blob upload vulnerable to credential forwarding via unvalidated Location header in oras.land/oras-go

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

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 CVE-2026-50151 has been found in oras.land/oras-go/v2.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade oras.land/oras-go/v2 to 2.6.1 or later.
If unsure, ask your IT team or search "oras.land/oras-go/v2 CVE-2026-50151" on the vendor's site.

CVE-2026-50151 (oras.land/oras-go/v2) — CWE-918 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.6.1 — apply immediately
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

SSRF (CWE-918) exists in oras.land/oras-go/v2.

📍 Affected scope

Check the vendor advisory for the affected versions of oras.land/oras-go/v2.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 2.6.1.

🛡️ 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 'oras.land/oras-go/v2' . 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. 1
    Identify exposure identify
    grep -r 'oras.land/oras-go/v2' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で oras.land/oras-go/v2 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade oras.land/oras-go/v2 to 2.6.1

    ステージング環境で 2.6.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go oras.land/oras-go/v2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.6.1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details