CVE-2026-86145Disclosure

LOWCVSS 8.2 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

Patch affected systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

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).

Back to dashboard

0.5/ 10 priority

Sources & remediation

Other references

Weakness type (CWE)

CWE-424

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Threat summary

Patch or workaround signal is available
1 mentions across 1 observed day

What's happening

Patch or workaround mentioned in 1 signal
Technical details provided in 1 signal
Disclosure: 1 classified signal
1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d

Signal classification1 categories

Disclosure

1100.0%

Full discourse1 post

Upwind Security MDR@UpwindMDR45d
Disclosure
🚨High - PCRE2 DFA Match OOB Write via Cached Workspace Reuse (CVE-2026-86145) PCRE2's pcre2_dfa_match() can reuse a cached workspace block during recursive DFA matching without a required size check, leading to an out-of-bounds write. Exploitation needs an attacker-controlled regex (recursive pattern) plus a small heap limit set via the API, enabling memory corruption and potential RCE. Non-recursive patterns without constrained heap limits are not impacted. 👉Affected: PCRE2 < 10.48 | Upgrade to 10.48
Post summary
The tweet announces CVE‑2026‑86145, a PCRE2 out‑of‑bounds write that may lead to RCE, and advises upgrading to version 10.48 for remediation.
0000063
303 followersView on X

Explore more

Back to dashboard