Malformed CAR panics and excessive memory usage

Exploitation

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

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact Versions impacted <= go-car@v0.3.3 <= go-car@v2.3.0 Description Decoding CAR data from untrusted user input can cause: - Panics: - Out of bound memory access - Out of memory - Divide by zero - Excessive memory usage Such panics can be triggered by intentionally malformed CARv1 data, including CARv1 data within a CARv2 container; and also CARv2 data with excessively large indexes. These vulnerabilities are not known to be exploited in the wild and were discovered primarily with the use of code fuzzing tooling. Details Out of bound memory access (OOB), out of memory (OOM) panics or excessive memory usage can be triggered by decode of malformed CARv1 headers, malformed CARv1 sections, and malformed CIDv0 data used in CARv1 sections. This also applies to CARv1 data within a CARv2 container. Additionally, we wish to use this security advisory to make clear to consumers of CARv2 format data that loading CARv2 indexes from untrusted sources is dangerous and should be avoided. Where…

Published by the source

6 Jul 2022, 19:26 UTC

Last modified by the source

14 Feb 2023, 21:32 UTC

Source last checked

26 Oct 2026, 14:55 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9x4h-8wgm-8xfg

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

# Patch Next advisory brief: GHSA-9x4h-8wgm-8xfg

Advisory: Malformed CAR panics and excessive memory usage
IDs: GHSA-9x4h-8wgm-8xfg
Record: https://patchnext.com/advisories/ghsa-9x4h-8wgm-8xfg (revision 1, source checked 26 Oct 2026, 14:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
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-car/v2 2.4.0; github.com/ipld/go-car 0.4.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/ipld/go-car/v2: affected >= 2.0.0, < 2.4.0; fixed in 2.4.0
- Go github.com/ipld/go-car: affected < 0.4.0; fixed in 0.4.0

## Suggested inspection (read-only)
- Go github.com/ipld/go-car/v2: check the installed version with your package manager.
- Go github.com/ipld/go-car: 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-car/v2, github.com/ipld/go-car.
- 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-9x4h-8wgm-8xfg (GitHub-reviewed advisory GHSA-9x4h-8wgm-8xfg lists affected ranges: Go github.com/ipld/go-car >=0 =2.0.0 <2.4.0)

Commands are suggestions: review each one before running it.