PCRE2 is a widely embedded regex library; an OOB write can crash or lead to code execution across many products, so broad patching is warranted.
CVE-2026-86145
PCRE2 out-of-bounds write via crafted regex may cause crashes or code execution
Is CVE-2026-86145 being exploited?
Not confirmed. CVE-2026-86145 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.
How severe is CVE-2026-86145?
CVE-2026-86145 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-86145?
Yes. A fix has been recorded for CVE-2026-86145. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-86145 affect?
CVE-2026-86145 affects PCRE2 < 10.48, Software embedding PCRE2 (web servers, apps, languages). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-86145?
Upgrade PCRE2 to 10.48+ and update/rebuild dependent packages
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker-controlled regex can trigger an out-of-bounds write in pcre2_dfa_match, allowing crashes and potential remote code execution in affected apps.
Patch when possible
- affected>= 10.32 and < 10.48
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.