Approved changes feed: RSS · Atom

cpe:2.3:a:protocol:go-ipld-prime:*:*:*:*:*:go:*:*

part: a version: * update: *

VendorProtocol (f2b98f42-7d41-5397-b702-40a5f7aae0b0)
ProductGo Ipld Prime (b43143db-ac66-5390-9a61-08c209f5c646)
Edition*
Language*
Software edition*
Target softwarego
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/ipld/go-ipld-prime purl2cpe 2026-06-01 10:18:11.539425
pkg:golang/github.com/ipld/go-ipld-prime purl2cpe 2026-06-01 10:18:11.539427

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-35480 vulnerable 2026-06-03 15:22:11.908186 go-ipld-prime's DAG-CBOR decoder unbounded memory allocation from CBOR headers
MEDIUM (6.2)
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.
Published: 2026-04-07T14:43:24.781Z
Updated: 2026-04-09T14:40:11.103Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-22460 vulnerable 2026-06-03 14:49:19.411239 go-ipld-prime json codec may panic if asked to encode bytes
HIGH (7.5)
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. Encoding data which contains a Bytes kind Node will pass a Bytes token to the JSON encoder which will panic as it doesn't expect to receive Bytes tokens. Such an encode should be treated as an error, as plain JSON should not be able to encode Bytes. This only impacts uses of the `json` codec. `dag-json` is not impacted. Use of `json` as a decoder is not impacted. This issue is fixed in v0.19.0. As a workaround, one may prefer the `dag-json` codec, which has the ability to encode bytes.
Published: 2023-01-04T14:53:19.877Z
Updated: 2025-03-11T13:34:55.463Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.