Categories
CVE-2026-42328 medium CVSS 6.2

Vulnerability in github.com/ipld/go-ipld-prime (CVE-2026-42328)

Summary

Vulnerability in github.com/ipld/go-ipld-prime (CVE-2026-42328). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.23.0 or later.

Original description

The description as published by the source.

go-ipld-prime is an implementation of the InterPlanetary Linked Data (IPLD) spec interfaces, a batteries-included codec implementations of IPLD for CBOR and JSON, and tooling for basic operations on IPLD objects. Prior to 0.23.0, the DAG-CBOR and DAG-JSON decoders recurse on each nested map or list without a depth limit. A payload containing deeply nested collections causes the decoder to recurse once per level, growing the goroutine stack until the Go runtime terminates the process with a fatal stack overflow (distinct from a recoverable panic). This vulnerability is fixed in 0.23.0.

Source: NIST National Vulnerability Database 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-42328 has been found in github.com/ipld/go-ipld-prime.
Risk of unauthorized operations or information disclosure. CVSS score: 6.2/10.
What to do: upgrade github.com/ipld/go-ipld-prime to 0.23.0 or later.
If unsure, ask your IT team or search "github.com/ipld/go-ipld-prime CVE-2026-42328" on the vendor's site.

CVE-2026-42328 (github.com/ipld/go-ipld-prime) — CWE-674 / CVSS v3 6.2
Attack vector: local / unauthenticated / no user interaction
Patched: 0.23.0 — 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

A vulnerability (CWE-674) exists in github.com/ipld/go-ipld-prime.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/ipld/go-ipld-prime.

🔥 Severity

Severity: Medium (CVSS 6.2/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.23.0.

🛡️ 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 'github.com/ipld/go-ipld-prime' . 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 'github.com/ipld/go-ipld-prime' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade github.com/ipld/go-ipld-prime to 0.23.0

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

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

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

Affected packages

go github.com/ipld/go-ipld-prime
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.23.0"}]}]

References

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