Bug 2568017 (CVE-2026-77299) - CVE-2026-77299 github.com/dlclark/regexp2: regexp2: Denial of Service via unbounded memory allocation during pattern matching
Summary: CVE-2026-77299 github.com/dlclark/regexp2: regexp2: Denial of Service via unb...
Keywords:
Status: NEW
Alias: CVE-2026-77299
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-06 01:41 UTC by OSIDB Bzimport
Modified: 2026-11-06 19:00 UTC (History)
66 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-06 01:41:16 UTC
Regexp2 is a feature-rich RegExp engine for Go. Prior to version 2.3.0, when regexp2 compiles and matches a pattern containing a large fixed-count quantifier applied to a zero-width subexpression — e.g. (?:){50000000} — the match engine executes the empty loop body m-1 times, pushing two integers onto the backtracking stack on every iteration. Because the parser accepts any repetition count up to math.MaxInt32 and the backtracking stack grows without bound, a pattern of fewer than 20 bytes matched against an empty input can force multi-gigabyte allocation and OOM-kill the process. MatchTimeout does not fully mitigate this because the memory is allocated faster than the 100 ms timeout clock can fire. This issue has been patched in version 2.3.0.


Note You need to log in before you can comment on or make changes to this bug.