dbcve.org
Go Ipld PrimeApplication · Protocol

CVE-2026-35480

MEDIUM · 6.2 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to 0.22.0 or later.
See remediation →
67/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.22.0, the DAG-CBOR decoder uses collection sizes declared in CBOR headers as Go preallocation hints for maps and lists. The decoder does not cap these size hints or account for their cost in its allocation budget, allowing small payloads to cause excessive memory allocation. This vulnerability is fixed in 0.22.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The go-ipld-prime DAG-CBOR decoder uses collection sizes from CBOR headers as Go preallocation hints for maps and lists without validating or capping these values. An attacker can craft small CBOR payloads with inflated size headers to trigger excessive memory allocation, causing resource exhaustion.

MitigationUpgrade go-ipld-prime to version 0.22.0 or later, which implements size cap enforcement for preallocation hints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Go Ipld PrimeApplication
Affected:< 0.22.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify go-ipld-prime version
    Run 'go list -m all | grep go-ipld-prime' or check the go.mod file for the go-ipld-prime entry
    Affected if The version listed is before 0.22.0 (e.g., 0.21.0, 0.20.0, etc.)
  2. Confirm CBOR decoding usage
    Search codebase for imports of 'github.com/ipld/go-ipld-prime' and usage of node parsing functions such as DagCbor().Decode or related CBOR unmarshaling methods
    Affected if The application uses the DAG-CBOR decoder from go-ipld-prime to parse CBOR data
  3. Check if input is untrusted
    Review whether CBOR data being decoded comes from network sources, user uploads, or other untrusted origins versus only trusted internal sources
    Affected if CBOR decoding processes data from untrusted or external sources that could contain crafted payloads
  4. Review memory consumption patterns
    Monitor application memory usage during CBOR decode operations, or review logs for OOM or memory allocation failure events
    Affected if Memory spikes or exhaustion occur when decoding CBOR payloads, particularly small payloads that claim large collection sizes

You are affected if go-ipld-prime version is below 0.22.0 AND your application uses the DAG-CBOR decoder to process untrusted CBOR data that could contain inflated size headers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.22.0 or later
Fixed in 0.22.0
Interim mitigation

Upgrade go-ipld-prime to version 0.22.0 or later, which implements size cap enforcement for preallocation hints.

Recommended fix High confidence

Upgrade to go-ipld-prime version 0.22.0

  1. Check the current version of go-ipld-prime in your project by running: go list -m all | grep github.com/ipld/go-ipld-prime
  2. Update go-ipld-prime to version 0.22.0 by running: go get github.com/ipld/[email protected]
  3. Run go mod tidy to clean up dependencies: go mod tidy
  4. Verify the upgrade by running: go list -m all | grep github.com/ipld/go-ipld-prime
  5. Rebuild and test your application to ensure compatibility: go build ./... && go test ./...

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Go Ipld Prime Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35480 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-35480 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data