Allocation of Resources Without Limits or Throttling Affecting ipfs-cluster package, versions <1.1.5-r13
Threat Intelligence
This vulnerability is trending on Twitter; this may indicate a growing threat.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CHAINGUARDLATEST-IPFSCLUSTER-16297755
- published26 Apr 2026
- disclosed7 Apr 2026
Introduced: 7 Apr 2026
CVE-2026-29181 (opens in a new tab)How to fix?
Upgrade Chainguard ipfs-cluster to version 1.1.5-r13 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream ipfs-cluster package and not the ipfs-cluster package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
OpenTelemetry-Go is the Go implementation of OpenTelemetry. From 1.36.0 to 1.40.0, multi-value baggage: header extraction parses each header field-value independently and aggregates members across values. This allows an attacker to amplify cpu and allocations by sending many baggage: header lines, even when each individual value is within the 8192-byte per-value parse limit. This vulnerability is fixed in 1.41.0.