rpm package
almalinux/pcre2-static
pkg:rpm/almalinux/pcre2-static
Vulnerabilities (7)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-103111 | Hig | 7.6 | < 10.44-1.5.el10_2 | 10.44-1.5.el10_2 | Sep 30, 2026 | 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-89161 | Hig | 7.4 | < 10.44-1.5.el10_2 | 10.44-1.5.el10_2 | Sep 11, 2026 | 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 | Low | 3.7 | < 10.44-1.5.el10_2 | 10.44-1.5.el10_2 | Sep 11, 2026 | 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 | Med | 6.5 | < 10.44-1.5.el10_2 | 10.44-1.5.el10_2 | Sep 11, 2026 | PCRE2 before 10.48, on 32-bit platforms, has a pcre2_compile_32 integer overflow and resultant out-of-bounds write. | |
| CVE-2026-89157 | Med | 5.7 | < 10.44-1.5.el10_2 | 10.44-1.5.el10_2 | Sep 11, 2026 | 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 | Low | 2.9 | < 10.44-1.5.el10_2 | 10.44-1.5.el10_2 | Sep 11, 2026 | 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 | Hig | 8.2 | < 10.44-1.5.el10_2 | 10.44-1.5.el10_2 | Sep 5, 2026 | 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 attac |
- affected < 10.44-1.5.el10_2fixed 10.44-1.5.el10_2
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.
- affected < 10.44-1.5.el10_2fixed 10.44-1.5.el10_2
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.
- affected < 10.44-1.5.el10_2fixed 10.44-1.5.el10_2
PCRE2 before 10.48 has a pcre2_match out-of-bounds read during the PCRE2_MATCH_INVALID_UTF matching of an invalid UTF subject.
- affected < 10.44-1.5.el10_2fixed 10.44-1.5.el10_2
PCRE2 before 10.48, on 32-bit platforms, has a pcre2_compile_32 integer overflow and resultant out-of-bounds write.
- affected < 10.44-1.5.el10_2fixed 10.44-1.5.el10_2
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.
- affected < 10.44-1.5.el10_2fixed 10.44-1.5.el10_2
PCRE2 before 10.48 has a pcre2_match out-of-bounds read after a JIT fallback when an attacker can provide invalid UTF data.
- affected < 10.44-1.5.el10_2fixed 10.44-1.5.el10_2
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 attac