PCRE PCRE2
8 published vulnerabilities name this product.
As the CNAs write it in their CVE records (vendor and product); the versions are theirs.
| CVE | Vulnerable versions | Title | Severity | Published | EPSS | Exploitation |
|---|---|---|---|---|---|---|
| CVE-2026-103111 | < 10.49 | PCRE2 before 10.49, when there is an attacker-controlled regular expression and certain JIT API usage, allows an out-of-bounds write with ar | HIGH 7.6 | 0.3 % | ||
| CVE-2026-89162 | 10.45 – < 10.48 | In PCRE2 before 10.48, pcre2_serialize_encode might disclose two bytes to an adversary, typically in a situation where the access available | LOW 3.3 | 0.2 % | ||
| CVE-2026-89161 | < 10.48 | In PCRE2 before 10.48, pcre2_jit_match mishandles a previously copied subject being passed in as a context. An incorrect free operation can | HIGH 7.8 | 0.1 % | ||
| CVE-2026-89160 | 10.34 – < 10.48 | PCRE2 before 10.48 has a pcre2_match out-of-bounds read during the PCRE2_MATCH_INVALID_UTF matching of an invalid UTF subject. | MEDIUM 6.5 | 0.3 % | ||
| CVE-2026-89158 | < 10.48 | PCRE2 before 10.48, on 32-bit platforms, has a pcre2_compile_32 integer overflow and resultant out-of-bounds write. | MEDIUM 6.5 | 0.2 % | ||
| CVE-2026-89157 | 10.30 – < 10.48 | PCRE2 before 10.48, on 32-bit platforms, has a pcre2_pattern_convert out-of-bounds write when an attacker can provide a large pattern. | HIGH 7.4 | 0.3 % | ||
| CVE-2026-89156 | 10.34 – < 10.48 | PCRE2 before 10.48 has a pcre2_match out-of-bounds read after a JIT fallback when an attacker can provide invalid UTF data. | MEDIUM 5.9 | 0.3 % | ||
| CVE-2026-86145 | 10.32 – < 10.48 | 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 works | HIGH 8.2 | 0.4 % |