Technical impact
The vulnerability resides in the Re2JS regular expression engine, a JavaScript port of the RE2 library. From version 2.2.0 through 2.8.6, enabling lookbehind constructs and performing repeated matching operations such as matcher().find(), matchAll(), split(), or matcher().replaceAll() can trigger quadratic total processing time. The underlying issue lies in how the engine restarts lookbehind scanning from the beginning for each start position, and in matcher-based APIs that request capture slots, which block early exit optimizations used for captureless patterns. Dense matches therefore repeatedly rescan large portions of the input, allowing maliciously crafted text to monopolize a single‑threaded worker and cause a denial of service. The weakness is an instance of CWE-1333 (Improper Limitation of Input Size) and CWE-407 (Uncontrolled Resource Consumption).
Affected Systems
Affected vendor and product: le0pard re2js. Versions affected include all releases from 2.2.0 up to but excluding 2.8.7, the first version to contain the fix. This impacts any software that incorporates the unpatched Re2JS library, especially web applications and services that interpret user input through the matcher APIs.
Risk and Exploitability
The CVSS base score of 7.5 reflects a high impact denial of service with medium to high exploitation potential. EPSS is not available, and the vulnerability is not listed in CISA’s KEV catalogue. Because the flaw is exercised when user-controllable data is fed to the regex engine, the attack vector is inferred to be remote, via any API endpoint that processes user input. An attacker needs only to send a crafted request containing a dense lookbehind pattern and malicious text; no additional privileges are required. The single‑threaded execution model means a single successful request can drain processor time, causing application unavailability until the request completes or the server is restarted.
Github GHSA