Veille CVE

Recherche « PCRE2 »

8 CVE

Critique 0 Élevée 4 Moyenne 3 Faible 1 Non évaluée 0 Exploitées (KEV) Tri : plus récentes « PCRE2 » ✕
  1. CVE-2026-103111 7.6 Élevée

    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.

  2. CVE-2026-89162 3.3 Faible

    PCRE2 · 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.

  3. CVE-2026-89161 7.8 Élevée

    PCRE2 · Pcre pcre2

    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.

  4. CVE-2026-89160 6.5 Moyenne

    PCRE2 · 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.

  5. CVE-2026-89158 6.5 Moyenne

    PCRE2 · Pcre pcre2

    PCRE2 before 10.48, on 32-bit platforms, has a pcre2_compile_32 integer overflow and resultant out-of-bounds write.

  6. CVE-2026-89157 7.4 Élevée

    PCRE2 · 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.

  7. CVE-2026-89156 5.9 Moyenne

    PCRE2 · 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.

  8. CVE-2026-86145 8.2 Élevée

    PCRE2

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