CVE-2026-12590 Affecting openclaw package, versions <2026.7.1-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.25% (17th percentile)

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-18164225
  • published22 Jul 2026
  • disclosed9 Jul 2026

Introduced: 9 Jul 2026

NewCVE-2026-12590  (opens in a new tab)

How to fix?

Upgrade Minimos:latest openclaw to version 2026.7.1-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.

Impact: In body-parser versions prior to 1.20.6 (1.x line) and 2.3.0 (2.x line), when the parser is configured with an invalid limit option value such as an unparseable string or NaN, bytes.parse returns null and the request body size check is silently skipped. Applications that rely on limit as their primary safeguard against oversized request bodies will accept arbitrarily large payloads, leading to excessive memory and CPU usage and denial of service. Patches: This issue is fixed in body-parser 1.20.6 and 2.3.0. After the fix, invalid limit values throw a clear error at parser construction time instead of silently disabling enforcement, while null and undefined continue to fall back to the default limit of 100kb. Workarounds: Validate the limit value before passing it to body-parser. For example, parse the value at startup and reject any configuration where the result is null or a non-finite number.

CVSS Base Scores

version 3.1