CVE-2026-86145
published 2026-09-05CVE-2026-86145: PCRE2 before 10.48 allows a pcre2_dfa_match out-of-bounds write because reuse of a cached workspace block, in a recursive DFA matching workspace, lacks a size…
PriorityP348high8.2CVSS 3.1
AVNACLPRNUINSUCNIHAL
EPSS
0.37%
30.6th percentile
PCRE2 before 10.48 allows a pcre2_dfa_match out-of-bounds write because reuse of a cached workspace block, in a recursive DFA matching workspace, lacks a size check (even though a newly allocated block, for the same purpose, does have a size check). This outcome requires an attacker-controlled regular expression, or a recursive pattern in conjunction with a small heap limit (this can be set through the API).
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| pcre | pcre2 | >= 10.32 < 10.48 | 10.48 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
PCRE PCRE2 up to 10.47 Recursive DFA Matching Workspace pcre2_dfa_match out-of-bounds write (Nessus ID 343097)
vuldb·2026-09-05·CVSS 8.2
CVE-2026-86145 [HIGH] PCRE PCRE2 up to 10.47 Recursive DFA Matching Workspace pcre2_dfa_match out-of-bounds write (Nessus ID 343097)
A vulnerability was found in PCRE PCRE2 up to 10.47. It has been classified as critical. This vulnerability affects the function pcre2_dfa_match of the component Recursive DFA Matching Workspace. The manipulation leads to out-of-bounds write.
This vulnerability is referenced as CVE-2026-86145. Remote exploitation of the attack is possible. No exploit is available.
Upgrading the affected component is recommended.
GHSA
PCRE2 before 10.48 allows a pcre2_dfa_match out-of-bounds write because reuse of a cached workspace block, in a recursive DFA matching workspace, lacks a size check (even though a newly allocated bloc
ghsa_unreviewed·2026-09-05
CVE-2026-86145 [HIGH] CWE-424 PCRE2 before 10.48 allows a pcre2_dfa_match out-of-bounds write because reuse of a cached workspace block, in a recursive DFA matching workspace, lacks a size check (even though a newly allocated bloc
PCRE2 before 10.48 allows a pcre2_dfa_match out-of-bounds write because reuse of a cached workspace block, in a recursive DFA matching workspace, lacks a size check (even though a newly allocated block, for the same purpose, does have a size check). This outcome requires an attacker-controlled regular expression, or a recursive pattern in conjunction with a small heap limit (this can be set through the API).
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-09-05
Published