ipld/go-codec-dagpb panics when processing certain blocks

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2022-2584: 0.77% estimated exploitation activity in the next 30 days; percentile 55.70 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Decoding certain blocks using the go-ipld-prime version of the dag-pb codec (go-codec-dagpb) can cause a panic. The panic comes from an assumption that the reported link length is accurate, but if the block ends before that reported length then it’s a buffer overread. Patches The issue is fixed in v1.3.1 and above. Consumers can discover the versions of go-codec-dagpb in a module's dependency graph using the following command in the module root: Workarounds You can work around this issue without upgrading by recovering panics higher in the call stack of the goroutine that calls the defective code. For more information If you have any questions or comments about this advisory: Ask in IPFS Discord #ipld-chatter Open an issue in go-codec-dagpb

Published by the source

8 Apr 2022, 22:08 UTC

Last modified by the source

23 Jan 2026, 22:34 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g3vv-g2j5-45f2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-2584

Advisory: ipld/go-codec-dagpb panics when processing certain blocks
IDs: CVE-2022-2584, GHSA-g3vv-g2j5-45f2
Record: https://patchnext.com/advisories/cve-2022-2584 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/ipld/go-codec-dagpb 1.3.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/ipld/go-codec-dagpb: affected < 1.3.1; fixed in 1.3.1

## Suggested inspection (read-only)
- Go github.com/ipld/go-codec-dagpb: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/ipld/go-codec-dagpb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-g3vv-g2j5-45f2 (GitHub-reviewed advisory GHSA-g3vv-g2j5-45f2 lists affected ranges: Go github.com/ipld/go-codec-dagpb >=0 <1.3.1)

Commands are suggestions: review each one before running it.