Pcre Pcre2 vulnerabilities
🔔 Create alert RSS Version checker
Published CVEs affecting Pcre Pcre2: 8 record(s), with affected versions and fixes.cpe:2.3:a:pcre:pcre2
CVE-2026-103111
High · 7.6
CWE-787 Sep 30, 2026
Out-of-bounds Write in Pcre Pcre2
PCRE2 before 10.49, when there is an attacker-controlled regular expression and certain JIT API usage, allows an out-of-bounds write with arbitrary data.
CVE-2026-89162
Low · 3.3
CWE-669 Sep 11, 2026
Incorrect Resource Transfer Between Spheres in Pcre Pcre2
In PCRE2 before 10.48, pcre2_serialize_encode might disclose two bytes to an adversary, typically in a situation where the access available to the adversary is already unsafe.
CVE-2026-89161
High · 7.8
CWE-590 Sep 11, 2026
In PCRE2 before 10.48, pcre2_jit_match mishandles a previously copied subject being…
In PCRE2 before 10.48, pcre2_jit_match mishandles a previously copied subject being passed in as a context. An incorrect free operation can occur.
CVE-2026-89160
Medium · 6.5
CWE-125 Sep 11, 2026
Out-of-bounds Read in Pcre Pcre2
PCRE2 before 10.48 has a pcre2_match out-of-bounds read during the PCRE2_MATCH_INVALID_UTF matching of an invalid UTF subject.
CVE-2026-89158
Medium · 6.5
CWE-190 Sep 11, 2026
Integer Overflow or Wraparound in Pcre Pcre2
PCRE2 before 10.48, on 32-bit platforms, has a pcre2_compile_32 integer overflow and resultant out-of-bounds write.
CVE-2026-89157
High · 7.4
CWE-190 Sep 11, 2026
Integer Overflow or Wraparound in Pcre Pcre2
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.
CVE-2026-89156
Medium · 5.9
CWE-125 Sep 11, 2026
Out-of-bounds Read in Pcre Pcre2
PCRE2 before 10.48 has a pcre2_match out-of-bounds read after a JIT fallback when an attacker can provide invalid UTF data.
CVE-2026-86145
High · 8.2
CWE-424 Sep 5, 2026
PCRE2 before 10.48 allows a pcre2_dfa_match out-of-bounds write because reuse of a…
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).