# DEBIAN-CVE-2026-86145: pcre2 security update

DEBIAN-CVE-2026-86145, released September 6, 2026, fixes 1 CVE in pcre2. None of them is reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/fix/linux/debian-cve-2026-86145
- Platform: Linux
- Released: Sep 6, 2026
- Priority: High (Closes CVE-2026-86145, high severity)
- CVEs: 1, exploited: 0, on CISA KEV: 0
- Vendor advisory: https://security-tracker.debian.org/tracker/CVE-2026-86145

## Applies to

| Product | Release | Fixed in |
|---|---|---|
| [pcre2](https://patchblox.com/security/data/product/linux/pcre2.md) | Debian 12.15 (bookworm) | 10.42-1+deb12u1 |
| [pcre2](https://patchblox.com/security/data/product/linux/pcre2.md) | Debian 13.5 (trixie) | 10.46-1~deb13u2 |
| [pcre2](https://patchblox.com/security/data/product/linux/pcre2.md) | Debian 14 | 10.48-1 |

## CVEs this fix closes

| CVE | Priority | Title | CVSS | EPSS | Exploitation |
|---|---|---|---:|---:|---|
| [CVE-2026-86145](https://patchblox.com/security/data/cve/CVE-2026-86145.md) | High | 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). | 8.2 | 0.0043 |  |

---

Data as of 2026-11-09T07:25:28Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.