USN-8974-1: pcre2 vulnerabilities
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)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/pcre2to a version that resolves this vulnerability.Fixed in 10.21-1ubuntu0.1~esm1 - Upgrade
Upgrade
ubuntu/pcre2to a version that resolves this vulnerability.Fixed in 10.31-2ubuntu0.1~esm2 - Upgrade
Upgrade
ubuntu/pcre2to a version that resolves this vulnerability.Fixed in 10.34-7ubuntu0.1+esm1 - Upgrade
Upgrade
ubuntu/pcre2to a version that resolves this vulnerability.Fixed in 10.39-3ubuntu0.2 - Upgrade
Upgrade
ubuntu/pcre2to a version that resolves this vulnerability.Fixed in 10.42-4ubuntu2.2 - Upgrade
Upgrade
ubuntu/pcre2to a version that resolves this vulnerability.Fixed in 10.46-1ubuntu1 - Upgrade
Upgrade
ubuntu/pcre2to a version that resolves this vulnerability.Fixed in 10.46-1ubuntu0.1 - Upgrade
Upgrade
ubuntu/libpcre2-16-0to a version that resolves this vulnerability.Fixed in 10.46-1ubuntu1 - Upgrade
Upgrade
ubuntu/libpcre2-32-0to a version that resolves this vulnerability.Fixed in 10.46-1ubuntu1 - Upgrade
Upgrade
ubuntu/libpcre2-8-0to a version that resolves this vulnerability.Fixed in 10.46-1ubuntu1 - Upgrade
Upgrade
ubuntu/libpcre2-devto a version that resolves this vulnerability.Fixed in 10.46-1ubuntu1 - Upgrade
Upgrade
ubuntu/libpcre2-posix3to a version that resolves this vulnerability.Fixed in 10.46-1ubuntu1 - Upgrade
Upgrade
ubuntu/pcre2-utilsto a version that resolves this vulnerability.Fixed in 10.46-1ubuntu1 - Upgrade
Upgrade
ubuntu/libpcre2-16-0to a version that resolves this vulnerability.Fixed in 10.46-1ubuntu0.1 - Upgrade
Upgrade
ubuntu/libpcre2-32-0to a version that resolves this vulnerability.Fixed in 10.46-1ubuntu0.1 - Upgrade
Upgrade
ubuntu/libpcre2-8-0to a version that resolves this vulnerability.Fixed in 10.46-1ubuntu0.1 - Upgrade
Upgrade
ubuntu/libpcre2-devto a version that resolves this vulnerability.Fixed in 10.46-1ubuntu0.1 - Upgrade
Upgrade
ubuntu/libpcre2-posix3to a version that resolves this vulnerability.Fixed in 10.46-1ubuntu0.1 - Upgrade
Upgrade
ubuntu/pcre2-utilsto a version that resolves this vulnerability.Fixed in 10.46-1ubuntu0.1 - Upgrade
Upgrade
ubuntu/libpcre2-16-0to a version that resolves this vulnerability.Fixed in 10.42-4ubuntu2.2 - Upgrade
Upgrade
ubuntu/libpcre2-32-0to a version that resolves this vulnerability.Fixed in 10.42-4ubuntu2.2 - Upgrade
Upgrade
ubuntu/libpcre2-8-0to a version that resolves this vulnerability.Fixed in 10.42-4ubuntu2.2 - Upgrade
Upgrade
ubuntu/libpcre2-devto a version that resolves this vulnerability.Fixed in 10.42-4ubuntu2.2 - Upgrade
Upgrade
ubuntu/libpcre2-posix3to a version that resolves this vulnerability.Fixed in 10.42-4ubuntu2.2 - Upgrade
Upgrade
ubuntu/pcre2-utilsto a version that resolves this vulnerability.Fixed in 10.42-4ubuntu2.2 - Upgrade
Upgrade
ubuntu/libpcre2-16-0to a version that resolves this vulnerability.Fixed in 10.39-3ubuntu0.2 - Upgrade
Upgrade
ubuntu/libpcre2-32-0to a version that resolves this vulnerability.Fixed in 10.39-3ubuntu0.2 - Upgrade
Upgrade
ubuntu/libpcre2-8-0to a version that resolves this vulnerability.Fixed in 10.39-3ubuntu0.2 - Upgrade
Upgrade
ubuntu/libpcre2-devto a version that resolves this vulnerability.Fixed in 10.39-3ubuntu0.2 - Upgrade
Upgrade
ubuntu/libpcre2-posix3to a version that resolves this vulnerability.Fixed in 10.39-3ubuntu0.2 - Upgrade
Upgrade
ubuntu/pcre2-utilsto a version that resolves this vulnerability.Fixed in 10.39-3ubuntu0.2 - Upgrade
Upgrade
ubuntu/libpcre2-16-0to a version that resolves this vulnerability.Fixed in Ubuntu Pro - Upgrade
Upgrade
ubuntu/libpcre2-32-0to a version that resolves this vulnerability.Fixed in Ubuntu Pro - Upgrade
Upgrade
ubuntu/libpcre2-8-0to a version that resolves this vulnerability.Fixed in Ubuntu Pro - Upgrade
Upgrade
ubuntu/libpcre2-devto a version that resolves this vulnerability.Fixed in Ubuntu Pro - Upgrade
Upgrade
ubuntu/libpcre2-posix2to a version that resolves this vulnerability.Fixed in Ubuntu Pro - Upgrade
Upgrade
ubuntu/pcre2-utilsto a version that resolves this vulnerability.Fixed in Ubuntu Pro - Upgrade
Upgrade
ubuntu/libpcre2-posix0to a version that resolves this vulnerability.Fixed in Ubuntu Pro - Upgrade
Upgrade
ubuntu/libpcre2-16-0to a version that resolves this vulnerability.Fixed in 10.21-1ubuntu0.1~esm1 - Upgrade
Upgrade
ubuntu/libpcre2-32-0to a version that resolves this vulnerability.Fixed in 10.21-1ubuntu0.1~esm1 - Upgrade
Upgrade
ubuntu/libpcre2-8-0to a version that resolves this vulnerability.Fixed in 10.21-1ubuntu0.1~esm1 - Upgrade
Upgrade
ubuntu/libpcre2-devto a version that resolves this vulnerability.Fixed in 10.21-1ubuntu0.1~esm1 - Upgrade
Upgrade
ubuntu/libpcre2-posix0to a version that resolves this vulnerability.Fixed in 10.21-1ubuntu0.1~esm1 - Upgrade
Upgrade
ubuntu/pcre2-utilsto a version that resolves this vulnerability.Fixed in 10.21-1ubuntu0.1~esm1
Event History
Child vulnerabilities
Contains the following vulnerabilities.
Frequently Asked Questions
Which Ubuntu releases are explicitly listed as affected by the memory-management and input-processing issues?
CVE-2026-86145 and CVE-2026-89156 explicitly affect Ubuntu 20.04 LTS, 22.04 LTS, 24.04 LTS, 26.04 LTS, and 26.10. Ubuntu 18.04 LTS is not listed for those two issues.
Does platform architecture change exposure to any of these issues?
Yes. CVE-2026-89157 is described as permitting possible arbitrary code execution specifically on 32-bit platforms when large patterns are handled; it explicitly affects Ubuntu 18.04 LTS through 26.10, including 26.10.
Which installed packages should be included when identifying systems that use the affected PCRE2 components?
Inventory the pcre2, pcre2-utils, libpcre2-8-0, libpcre2-16-0, libpcre2-32-0, libpcre2-posix3, and libpcre2-dev packages. Systems using these packages on the explicitly listed Ubuntu releases should be prioritized for remediation.
What security impact should triage account for?
The reported impacts include possible arbitrary code execution for CVE-2026-86145, CVE-2026-89157, and CVE-2026-89158, and possible denial of service for CVE-2026-89156. Exploitation is described in connection with processing attacker-controlled patterns or input, with large patterns specifically relevant to CVE-2026-89157.