Linux
pcre2 security updates
Patch Radar has 66 security fixes for pcre2, closing 13 CVEs. The newest security fix is ALAS2023-2026-3269 (10.40-1.amzn2023.0.5), released November 7, 2026.
Latest version
n/a
Release date not known
Security fixes
66
On record in Patch Radar
CVEs
13
Closed by those fixes
Exploited
0
Vendor report or CISA KEV
Security fixes, newest first
| Priority | Fix | Release | Fixed in | CVEs | Exploited | Released |
|---|---|---|---|---|---|---|
| High | ALAS2023-2026-3269 | amzn 2023 | 10.40-1.amzn2023.0.5 | 4 | Nov 7, 2026 | |
| High | ELSA-2026-81522 | ol 10 | 0:10.44-1.5.0.1.el10_2 | 7 | Nov 7, 2026 | |
| High | ELSA-2026-81532 | ol 9 | 0:10.40-7.0.1.el9_8 | 7 | Nov 7, 2026 | |
| High | ELSA-2026-81613 | ol 8 | 0:10.32-4.el8_10 | 4 | Nov 7, 2026 | |
| High | ALSA-2026:81532 | almalinux 9 | 10.40-7.el9_8 | 7 | Nov 7, 2026 | |
| High | ALSA-2026:81613 | almalinux 8 | 10.32-4.el8_10 | 4 | Nov 7, 2026 | |
| High | ALSA-2026:81522 | almalinux 10 | 10.44-1.5.el10_2 | 7 | Nov 7, 2026 | |
| High | RLSA-2026:81532 | rocky 9 | 0:10.40-7.el9_8 | 7 | Nov 7, 2026 | |
| High | RLSA-2026:81522 | rocky 10 | 0:10.44-1.5.el10_2 | 7 | Nov 7, 2026 | |
| High | RLSA-2026:81613 | rocky 8 | 0:10.32-4.el8_10 | 4 | Nov 7, 2026 | |
| High | RHSA-2026:81532 | RHEL 9 | 0:10.40-7.el9_8 | 7 | Oct 13, 2026 | |
| High | RHSA-2026:86205 | RHEL 10 | 10.44-1.4.el10_0 | 3 | Oct 13, 2026 | |
| High | RHSA-2026:81613 | RHEL 8 | 0:10.32-4.el8_10 | 4 | Oct 13, 2026 | |
| High | DEBIAN-CVE-2026-103111 | Debian 13.5 (trixie) | 10.46-1~deb13u3 | 1 | Oct 1, 2026 | |
| High | DEBIAN-CVE-2026-103111 | Debian 12.15 (bookworm) | 10.42-1+deb12u2 | 1 | Oct 1, 2026 | |
| High | DEBIAN-CVE-2026-103111 | Debian 14 | 10.48-3.1 | 1 | Oct 1, 2026 | |
| High | ALAS2023-2026-3119 | amzn 2023 | 10.40-1.amzn2023.0.4 | 1 | Sep 28, 2026 | |
| High | SUSE-SU-2026:23906-1 | sles 16.0 | 10.45-160000.4.1 | 7 | Sep 23, 2026 | |
| High | OPENSUSE-SU-2026:21938-1 | opensuse-leap 16.0 | 10.45-160000.4.1 | 7 | Sep 23, 2026 | |
| High | SUSE-SU-2026:4241-1 | sles 15.6 | 10.42-150600.3.3.1 | 6 | Sep 17, 2026 | |
| High | SUSE-SU-2026:4241-1 | sles 15.7 | 10.42-150600.3.3.1 | 6 | Sep 17, 2026 | |
| High | DEBIAN-CVE-2026-89157 | Debian 12.15 (bookworm) | 10.42-1+deb12u1 | 1 | Sep 11, 2026 | |
| High | DEBIAN-CVE-2026-89157 | Debian 13.5 (trixie) | 10.46-1~deb13u2 | 1 | Sep 11, 2026 | |
| High | DEBIAN-CVE-2026-89157 | Debian 14 | 10.48-1 | 1 | Sep 11, 2026 | |
| High | DEBIAN-CVE-2026-89156 | Debian 12.15 (bookworm) | 10.42-1+deb12u1 | 1 | Sep 11, 2026 | |
| High | DEBIAN-CVE-2026-89156 | Debian 13.5 (trixie) | 10.46-1~deb13u2 | 1 | Sep 11, 2026 | |
| High | DEBIAN-CVE-2026-89156 | Debian 14 | 10.48-1 | 1 | Sep 11, 2026 | |
| High | DEBIAN-CVE-2026-89160 | Debian 14 | 10.48-1 | 1 | Sep 11, 2026 | |
| High | DEBIAN-CVE-2026-89160 | Debian 12.15 (bookworm) | 10.42-1+deb12u1 | 1 | Sep 11, 2026 | |
| High | DEBIAN-CVE-2026-89160 | Debian 13.5 (trixie) | 10.46-1~deb13u2 | 1 | Sep 11, 2026 | |
| High | DEBIAN-CVE-2026-89158 | Debian 12.15 (bookworm) | 10.42-1+deb12u1 | 1 | Sep 11, 2026 | |
| High | DEBIAN-CVE-2026-89158 | Debian 13.5 (trixie) | 10.46-1~deb13u2 | 1 | Sep 11, 2026 | |
| High | DEBIAN-CVE-2026-89158 | Debian 14 | 10.48-1 | 1 | Sep 11, 2026 | |
| High | DEBIAN-CVE-2026-89161 | Debian 12.15 (bookworm) | 10.42-1+deb12u1 | 1 | Sep 11, 2026 | |
| High | DEBIAN-CVE-2026-89161 | Debian 13.5 (trixie) | 10.46-1~deb13u2 | 1 | Sep 11, 2026 | |
| High | DEBIAN-CVE-2026-89161 | Debian 14 | 10.48-1 | 1 | Sep 11, 2026 | |
| Routine | DEBIAN-CVE-2026-89162 | Debian 13.5 (trixie) | 10.46-1~deb13u2 | 1 | Sep 11, 2026 | |
| Routine | DEBIAN-CVE-2026-89162 | Debian 14 | 10.48-1 | 1 | Sep 11, 2026 | |
| High | RHSA-2026:81522 | RHEL 10 | 10.44-1.5.el10_2 | 4 | Sep 11, 2026 | |
| High | DEBIAN-CVE-2026-86145 | Debian 12.15 (bookworm) | 10.42-1+deb12u1 | 1 | Sep 6, 2026 | |
| High | DEBIAN-CVE-2026-86145 | Debian 14 | 10.48-1 | 1 | Sep 6, 2026 | |
| High | DEBIAN-CVE-2026-86145 | Debian 13.5 (trixie) | 10.46-1~deb13u2 | 1 | Sep 6, 2026 | |
| High | OPENSUSE-SU-2026:20512-1 | opensuse-leap 16.0 | 10.45-160000.3.1 | 1 | Apr 10, 2026 | |
| High | SUSE-SU-2026:21172-1 | sles 16.0 | 10.45-160000.3.1 | 1 | Apr 10, 2026 | |
| High | DEBIAN-CVE-2025-58050 | Debian 13.5 (trixie) | 10.46-1~deb13u1 | 1 | Aug 27, 2025 | |
| High | DEBIAN-CVE-2025-58050 | Debian 14 | 10.46-1 | 1 | Aug 27, 2025 | |
| High | ALAS2023-2023-286 | amzn 2023 | 10.40-1.amzn2023.0.3 | 1 | Aug 3, 2023 | |
| High | DEBIAN-CVE-2022-41409 | Debian 12.15 (bookworm) | 10.42-1 | 1 | Jul 18, 2023 | |
| High | DEBIAN-CVE-2022-41409 | Debian 13.5 (trixie) | 10.42-1 | 1 | Jul 18, 2023 | |
| High | DEBIAN-CVE-2022-41409 | Debian 14 | 10.42-1 | 1 | Jul 18, 2023 | |
| High | ALAS2023-2023-045 | amzn 2023 | 10.40-1.amzn2023.0.2 | 2 | Feb 17, 2023 | |
| High | ALSA-2022:5809 | almalinux 8 | 10.32-3.el8_6 | 1 | Aug 3, 2022 | |
| High | RHSA-2022:5809 | RHEL 8 | 0:10.32-3.el8_6 | 1 | Aug 3, 2022 | |
| High | RLSA-2022:5809 | rocky 8 | 0:10.32-3.el8_6 | 1 | Aug 2, 2022 | |
| High | ELSA-2022-5809 | ol 8 | 0:10.32-3.el8_6 | 1 | Aug 2, 2022 | |
| High | RHSA-2022:5251 | RHEL 9 | 0:10.37-5.el9_0 | 2 | Jul 1, 2022 | |
| High | ELSA-2022-5251 | ol 9 | 0:10.37-5.el9_0 | 2 | Jun 30, 2022 | |
| High | RLSA-2022:5251 | rocky 9 | 0:10.37-5.el9_0 | 2 | Jun 28, 2022 | |
| High | DEBIAN-CVE-2022-1586 | Debian 12.15 (bookworm) | 10.40-1 | 1 | May 16, 2022 | |
| High | DEBIAN-CVE-2022-1586 | Debian 13.5 (trixie) | 10.40-1 | 1 | May 16, 2022 | |
| High | DEBIAN-CVE-2022-1586 | Debian 14 | 10.40-1 | 1 | May 16, 2022 | |
| High | DEBIAN-CVE-2022-1587 | Debian 12.15 (bookworm) | 10.40-1 | 1 | May 16, 2022 | |
| High | DEBIAN-CVE-2022-1587 | Debian 13.5 (trixie) | 10.40-1 | 1 | May 16, 2022 | |
| High | DEBIAN-CVE-2022-1587 | Debian 14 | 10.40-1 | 1 | May 16, 2022 | |
| High | ELSA-2020-4539 | ol 8 | 0:10.32-2.el8 | 1 | Nov 10, 2020 | |
| High | RHSA-2020:4539 | RHEL 8 | 0:10.32-2.el8 | 1 | Nov 4, 2020 |
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.