CVE-2026-86145

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

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

PCRE2 is a re-working of the original PCRE1 library to provide an entirely new API. Since its initial release in 2015, there has been further development of the code and it now differs from PCRE1 in more than just the API. PCRE2 is written in C, and it has its own API. There are three sets of functions, one for the 8-bit library, which processes strings of bytes, one for the 16-bit library, which processes strings of 16-bit values, and one for the 32-bit library, which processes strings of 32-bit values. Unlike PCRE1, there are no C++ wrappers.

Security Fix(es):

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).(CVE-2026-86145)

PCRE2 is a re-working of the original PCRE1 library to provide an entirely new API. Since its initial release in 2015, there has been further development of the code and it now differs from PCRE1 in more than just the API. PCRE2 is written in C, and it has its own API. There are three sets of functions, one for the 8-bit library, which processes strings of bytes, one for the 16-bit library, which processes strings of 16-bit values, and one for the 32-bit library, which processes strings of 32-bit values. Unlike PCRE1, there are no C++ wrappers.

Security Fix(es):

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).(CVE-2026-86145)

PCRE2 is a re-working of the original PCRE1 library to provide an entirely new API. Since its initial release in 2015, there has been further development of the code and it now differs from PCRE1 in more than just the API. PCRE2 is written in C, and it has its own API. There are three sets of functions, one for the 8-bit library, which processes strings of bytes, one for the 16-bit library, which processes strings of 16-bit values, and one for the 32-bit library, which processes strings of 32-bit values. Unlike PCRE1, there are no C++ wrappers.

Security Fix(es):

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).(CVE-2026-86145)

PCRE2 is a re-working of the original PCRE1 library to provide an entirely new API. Since its initial release in 2015, there has been further development of the code and it now differs from PCRE1 in more than just the API. PCRE2 is written in C, and it has its own API. There are three sets of functions, one for the 8-bit library, which processes strings of bytes, one for the 16-bit library, which processes strings of 16-bit values, and one for the 32-bit library, which processes strings of 32-bit values. Unlike PCRE1, there are no C++ wrappers.

Security Fix(es):

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).(CVE-2026-86145)

PCRE2 is a re-working of the original PCRE1 library to provide an entirely new API. Since its initial release in 2015, there has been further development of the code and it now differs from PCRE1 in more than just the API. PCRE2 is written in C, and it has its own API. There are three sets of functions, one for the 8-bit library, which processes strings of bytes, one for the 16-bit library, which processes strings of 16-bit values, and one for the 32-bit library, which processes strings of 32-bit values. Unlike PCRE1, there are no C++ wrappers.

Security Fix(es):

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).(CVE-2026-86145)

The pcre2 package contains a new generation of the Perl Compatible Regular Expression libraries for implementing regular expression pattern matching using the same syntax and semantics as Perl.

Security Fix(es):

• pcre2: PCRE2: Out-of-bounds write allows arbitrary code execution via crafted regular expressions (CVE-2026-86145)

• PCRE2: PCRE2: Out-of-bounds read via invalid UTF data during JIT fallback (CVE-2026-89156)

• pcre2: PCRE2: Out-of-bounds write via large pattern input (CVE-2026-89157)

• pcre2: PCRE2: Denial of Service via out-of-bounds read during invalid UTF matching (CVE-2026-89160)

• PCRE2: PCRE2: Out-of-bounds write via integer overflow on 32-bit platforms (CVE-2026-89158)

• pcre2: PCRE2: Memory corruption vulnerability in pcre2_jit_match (CVE-2026-89161)

• pcre2: pcre2: Out-of-bounds write via crafted regular expression (CVE-2026-103111)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The pcre2 package contains a new generation of the Perl Compatible Regular Expression libraries for implementing regular expression pattern matching using the same syntax and semantics as Perl.

Security Fix(es):

• pcre2: PCRE2: Out-of-bounds write allows arbitrary code execution via crafted regular expressions (CVE-2026-86145)

• PCRE2: PCRE2: Out-of-bounds read via invalid UTF data during JIT fallback (CVE-2026-89156)

• pcre2: PCRE2: Out-of-bounds write via large pattern input (CVE-2026-89157)

• pcre2: PCRE2: Denial of Service via out-of-bounds read during invalid UTF matching (CVE-2026-89160)

• PCRE2: PCRE2: Out-of-bounds write via integer overflow on 32-bit platforms (CVE-2026-89158)

• pcre2: PCRE2: Memory corruption vulnerability in pcre2_jit_match (CVE-2026-89161)

• pcre2: pcre2: Out-of-bounds write via crafted regular expression (CVE-2026-103111)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The pcre2 package contains a new generation of the Perl Compatible Regular Expression libraries for implementing regular expression pattern matching using the same syntax and semantics as Perl.

Security Fix(es):

• pcre2: PCRE2: Out-of-bounds write allows arbitrary code execution via crafted regular expressions (CVE-2026-86145)

• pcre2: PCRE2: Out-of-bounds write via large pattern input (CVE-2026-89157)

• PCRE2: PCRE2: Out-of-bounds write via integer overflow on 32-bit platforms (CVE-2026-89158)

• pcre2: pcre2: Out-of-bounds write via crafted regular expression (CVE-2026-103111)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

MariaDB is a community developed fork from MySQL - a multi-user, multi-threaded SQL database server. It is a client/server implementation consisting of a server daemon (mariadbd) and many different client programs and libraries. The base package contains the standard MariaDB/MySQL client programs and utilities.

Security Fix(es):

• pcre2: PCRE2: Out-of-bounds write allows arbitrary code execution via crafted regular expressions (CVE-2026-86145)

• pcre2: PCRE2: Memory corruption vulnerability in pcre2_jit_match (CVE-2026-89161)

• pcre2: pcre2: Out-of-bounds write via crafted regular expression (CVE-2026-103111)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

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

The pcre2 package contains a new generation of the Perl Compatible Regular Expression libraries for implementing regular expression pattern matching using the same syntax and semantics as Perl.

Security Fix(es):

• pcre2: PCRE2: Out-of-bounds write allows arbitrary code execution via crafted regular expressions (CVE-2026-86145)
• PCRE2: PCRE2: Out-of-bounds read via invalid UTF data during JIT fallback (CVE-2026-89156)
• pcre2: PCRE2: Out-of-bounds write via large pattern input (CVE-2026-89157)
• pcre2: PCRE2: Denial of Service via out-of-bounds read during invalid UTF matching (CVE-2026-89160)
• PCRE2: PCRE2: Out-of-bounds write via integer overflow on 32-bit platforms (CVE-2026-89158)
• pcre2: PCRE2: Memory corruption vulnerability in pcre2_jit_match (CVE-2026-89161)
• pcre2: pcre2: Out-of-bounds write via crafted regular expression (CVE-2026-103111)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The pcre2 package contains a new generation of the Perl Compatible Regular Expression libraries for implementing regular expression pattern matching using the same syntax and semantics as Perl.

Security Fix(es):

• pcre2: PCRE2: Out-of-bounds write allows arbitrary code execution via crafted regular expressions (CVE-2026-86145)
• PCRE2: PCRE2: Out-of-bounds read via invalid UTF data during JIT fallback (CVE-2026-89156)
• pcre2: PCRE2: Out-of-bounds write via large pattern input (CVE-2026-89157)
• pcre2: PCRE2: Denial of Service via out-of-bounds read during invalid UTF matching (CVE-2026-89160)
• PCRE2: PCRE2: Out-of-bounds write via integer overflow on 32-bit platforms (CVE-2026-89158)
• pcre2: PCRE2: Memory corruption vulnerability in pcre2_jit_match (CVE-2026-89161)
• pcre2: pcre2: Out-of-bounds write via crafted regular expression (CVE-2026-103111)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

The pcre2 package contains a new generation of the Perl Compatible Regular Expression libraries for implementing regular expression pattern matching using the same syntax and semantics as Perl.

Security Fix(es):

• pcre2: PCRE2: Out-of-bounds write allows arbitrary code execution via crafted regular expressions (CVE-2026-86145)
• pcre2: PCRE2: Out-of-bounds write via large pattern input (CVE-2026-89157)
• PCRE2: PCRE2: Out-of-bounds write via integer overflow on 32-bit platforms (CVE-2026-89158)
• pcre2: pcre2: Out-of-bounds write via crafted regular expression (CVE-2026-103111)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

MariaDB is a community developed fork from MySQL - a multi-user, multi-threaded SQL database server. It is a client/server implementation consisting of a server daemon (mariadbd) and many different client programs and libraries. The base package contains the standard MariaDB/MySQL client programs and utilities.

Security Fix(es):

• pcre2: PCRE2: Out-of-bounds write allows arbitrary code execution via crafted regular expressions (CVE-2026-86145)
• pcre2: PCRE2: Memory corruption vulnerability in pcre2_jit_match (CVE-2026-89161)
• pcre2: pcre2: Out-of-bounds write via crafted regular expression (CVE-2026-103111)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

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

Out-of-bounds write in pcre2_dfa_match() with recursive patterns under a low heap limit (CVE-2026-86145).

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). (CVE-2026-86145) PCRE2: out-of-bounds write in JIT matching with large stack allocations. (CVE-2026-103111)

This update for pcre2 fixes the following issues:

• CVE-2026-86145: missing size checks in pcre2_dfa_match code can lead to an out-of-bounds write (bsc#1279893).
• CVE-2026-89156: out-of-bounds read via invalid UTF data during JIT fallback (bsc#1280054).
• CVE-2026-89157: out-of-bounds write via large pattern input (bsc#1280053).
• CVE-2026-89158: out-of-bounds write due to integer overflow in pcre2_compile_32 for 32-bit platforms (bsc#1280052).
• CVE-2026-89160: out-of-bounds read during the PCRE2_MATCH_INVALID_UTF matching of an invalid UTF subject (bsc#1280051).
• CVE-2026-89161: incorrect free operation due to mishandling of a previously copied subject in pcre2_jit_match (bsc#1280050).
• CVE-2026-89162: information disclosure via pcre2_serialize_encode (bsc#1280049).

Root has patched CVE-2026-86145 in the pcre2 package for Root:Debian:13. Multiple fixed versions available.

This update for pcre2 fixes the following issues:

• CVE-2026-86145: missing size checks in pcre2_dfa_match code can lead to an out-of-bounds write (bsc#1279893).
• CVE-2026-89156: out-of-bounds read via invalid UTF data during JIT fallback (bsc#1280054).
• CVE-2026-89157: out-of-bounds write via large pattern input (bsc#1280053).
• CVE-2026-89158: out-of-bounds write due to integer overflow in pcre2_compile_32 for 32-bit platforms (bsc#1280052).
• CVE-2026-89160: out-of-bounds read during the PCRE2_MATCH_INVALID_UTF matching of an invalid UTF subject (bsc#1280051).
• CVE-2026-89161: incorrect free operation due to mishandling of a previously copied subject in pcre2_jit_match (bsc#1280050).

This update for pcre2 fixes the following issues:

• CVE-2026-86145: missing size checks in pcre2_dfa_match code can lead to an out-of-bounds write (bsc#1279893).
• CVE-2026-89156: out-of-bounds read via invalid UTF data during JIT fallback (bsc#1280054).
• CVE-2026-89157: out-of-bounds write via large pattern input (bsc#1280053).
• CVE-2026-89158: out-of-bounds write due to integer overflow in pcre2_compile_32 for 32-bit platforms (bsc#1280052).
• CVE-2026-89160: out-of-bounds read during the PCRE2_MATCH_INVALID_UTF matching of an invalid UTF subject (bsc#1280051).
• CVE-2026-89161: incorrect free operation due to mishandling of a previously copied subject in pcre2_jit_match (bsc#1280050).

This update for pcre2 fixes the following issues:

• CVE-2026-86145: missing size checks in pcre2_dfa_match code can lead to an out-of-bounds write (bsc#1279893).
• CVE-2026-89156: out-of-bounds read via invalid UTF data during JIT fallback (bsc#1280054).
• CVE-2026-89157: out-of-bounds write via large pattern input (bsc#1280053).
• CVE-2026-89158: out-of-bounds write due to integer overflow in pcre2_compile_32 for 32-bit platforms (bsc#1280052).
• CVE-2026-89160: out-of-bounds read during the PCRE2_MATCH_INVALID_UTF matching of an invalid UTF subject (bsc#1280051).
• CVE-2026-89161: incorrect free operation due to mishandling of a previously copied subject in pcre2_jit_match (bsc#1280050).
• CVE-2026-89162: information disclosure via pcre2_serialize_encode (bsc#1280049).

This update for pcre2 fixes the following issues:

• CVE-2026-86145: missing size checks in pcre2_dfa_match code can lead to an out-of-bounds write (bsc#1279893).
• CVE-2026-89156: out-of-bounds read via invalid UTF data during JIT fallback (bsc#1280054).
• CVE-2026-89157: out-of-bounds write via large pattern input (bsc#1280053).
• CVE-2026-89158: out-of-bounds write due to integer overflow in pcre2_compile_32 for 32-bit platforms (bsc#1280052).
• CVE-2026-89160: out-of-bounds read during the PCRE2_MATCH_INVALID_UTF matching of an invalid UTF subject (bsc#1280051).
• CVE-2026-89161: incorrect free operation due to mishandling of a previously copied subject in pcre2_jit_match (bsc#1280050).
• CVE-2026-89162: information disclosure via pcre2_serialize_encode (bsc#1280049).

This update for pcre2 fixes the following issues:

• CVE-2026-86145: missing size checks in pcre2_dfa_match code can lead to an out-of-bounds write (bsc#1279893).
• CVE-2026-89156: out-of-bounds read via invalid UTF data during JIT fallback (bsc#1280054).
• CVE-2026-89157: out-of-bounds write via large pattern input (bsc#1280053).
• CVE-2026-89158: out-of-bounds write due to integer overflow in pcre2_compile_32 for 32-bit platforms (bsc#1280052).
• CVE-2026-89160: out-of-bounds read during the PCRE2_MATCH_INVALID_UTF matching of an invalid UTF subject (bsc#1280051).
• CVE-2026-89161: incorrect free operation due to mishandling of a previously copied subject in pcre2_jit_match (bsc#1280050).

This update for pcre2 fixes the following issues:

• CVE-2026-86145: missing size checks in pcre2_dfa_match code can lead to an out-of-bounds write (bsc#1279893).
• CVE-2026-89156: out-of-bounds read via invalid UTF data during JIT fallback (bsc#1280054).
• CVE-2026-89157: out-of-bounds write via large pattern input (bsc#1280053).
• CVE-2026-89158: out-of-bounds write due to integer overflow in pcre2_compile_32 for 32-bit platforms (bsc#1280052).
• CVE-2026-89160: out-of-bounds read during the PCRE2_MATCH_INVALID_UTF matching of an invalid UTF subject (bsc#1280051).
• CVE-2026-89161: incorrect free operation due to mishandling of a previously copied subject in pcre2_jit_match (bsc#1280050).

This update for pcre2 fixes the following issues:

• CVE-2026-86145: missing size checks in pcre2_dfa_match code can lead to an out-of-bounds write (bsc#1279893).
• CVE-2026-89156: out-of-bounds read via invalid UTF data during JIT fallback (bsc#1280054).
• CVE-2026-89157: out-of-bounds write via large pattern input (bsc#1280053).
• CVE-2026-89158: out-of-bounds write due to integer overflow in pcre2_compile_32 for 32-bit platforms (bsc#1280052).
• CVE-2026-89160: out-of-bounds read during the PCRE2_MATCH_INVALID_UTF matching of an invalid UTF subject (bsc#1280051).
• CVE-2026-89161: incorrect free operation due to mishandling of a previously copied subject in pcre2_jit_match (bsc#1280050).

It was discovered that PCRE2 did not correctly manage memory when processing certain patterns. An attacker could possibly use this issue to execute arbitrary code. This issue only affected Ubuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, Ubuntu 26.04 LTS, and Ubuntu 26.10. (CVE-2026-86145)

Albert Zhang discovered that PCRE2 did not correctly process certain input. An attacker could possibly use this issue to cause a denial of service. This issue only affected Ubuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, Ubuntu 26.04 LTS, and Ubuntu 26.10. (CVE-2026-89156)

It was discovered that PCRE2 did not correctly handle large patterns. On 32-bit platforms, an attacker could possibly use this issue to execute arbitrary code. This issue only affected Ubuntu 18.04 LTS, Ubuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, Ubuntu 26.04 LTS, and Ubuntu 26.10. (CVE-2026-89157)

It was discovered that PCRE2 did not correctly handle certain patterns. An attacker could possibly use this issue to execute arbitrary code. (CVE-2026-89158)

Ilia Alshanetsky discovered that PCRE2 did not correctly handle certain input. An attacker could possibly use this issue to cause a denial of service. This issue only affected Ubuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, Ubuntu 26.04 LTS, and Ubuntu 26.10. (CVE-2026-89160)

It was discovered that PCRE2 did not correctly manage memory when handling certain patterns. An attacker could possibly use this issue to execute arbitrary code. This issue only affected Ubuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, Ubuntu 26.04 LTS, and Ubuntu 26.10. (CVE-2026-89161)

It was discovered that PCRE2 could expose uninitialized data in certain circumstances. A local attacker could possibly use this issue to obtain sensitive information. This issue only affected Ubuntu 26.04 LTS and Ubuntu 26.10. (CVE-2026-89162)

Michael Allen discovered that PCRE2 did not correctly manage memory when using just-in-time compilation. An attacker could possibly use this issue to execute arbitrary code. This issue only affected Ubuntu 18.04 LTS, Ubuntu 20.04 LTS, Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, Ubuntu 26.04 LTS, and Ubuntu 26.10. (CVE-2026-103111)