Allocation of Resources Without Limits or Throttling Affecting openclaw package, versions <2026.6.9-r0
Threat Intelligence
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-MINIMOSLATEST-OPENCLAW-17392479
- published22 Jun 2026
- disclosed22 Jun 2026
Introduced: 22 Jun 2026
NewCVE-2026-54285 (opens in a new tab)How to fix?
Upgrade Minimos:latest openclaw to version 2026.6.9-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream openclaw package and not the openclaw package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
opentelemetry-js is the OpenTelemetry JavaScript Client. Prior to 2.8.0, W3CBaggagePropagator.extract() in @opentelemetry/core does not enforce size limits when parsing inbound baggage HTTP headers. The W3C Baggage specification recommends a maximum of 8,192 bytes and 180 entries; these limits were only enforced on the outbound (inject()) path, not on the inbound (extract()) path. Parsing oversized baggage causes memory allocation proportional to the header size without any cap. This vulnerability is fixed in 2.8.0.