Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
7.4
openeuler pcre2 may read/write outside memory
published 1 month ago
Summary
The PCRE2 library used in openEuler can mistakenly read or write past the intended data boundaries when it handles malformed text or large patterns, especially on 32-bit systems. This could cause a program to crash or be manipulated by an attacker. Update PCRE2 to version 10.48 or later to fix the problem.
What to do
- Update openeuler pcre2 to version 10.42-20.oe2403sp4.
- Update openeuler pcre2 to version 10.35-17.oe2003sp4.
- Update openeuler pcre2 to version 10.39-24.oe2203sp4.
- Update openeuler pcre2 to version 10.42-20.oe2403sp1.
- Update openeuler pcre2 to version 10.42-20.oe2403sp3.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| openEuler:24.03-LTS-SP4 | openeuler | pcre2 |
< 10.42-20.oe2403sp4 Fix: upgrade to 10.42-20.oe2403sp4
|
| openEuler:20.03-LTS-SP4 | openeuler | pcre2 |
< 10.35-17.oe2003sp4 Fix: upgrade to 10.35-17.oe2003sp4
|
| openEuler:22.03-LTS-SP4 | openeuler | pcre2 |
< 10.39-24.oe2203sp4 Fix: upgrade to 10.39-24.oe2203sp4
|
| openEuler:24.03-LTS-SP1 | openeuler | pcre2 |
< 10.42-20.oe2403sp1 Fix: upgrade to 10.42-20.oe2403sp1
|
| openEuler:24.03-LTS-SP3 | openeuler | pcre2 |
< 10.42-20.oe2403sp3 Fix: upgrade to 10.42-20.oe2403sp3
|
Original advisory text
pcre2 security update
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 has a pcre2_match out-of-bounds read after a JIT fallback when an attacker can provide invalid UTF data.(CVE-2026-89156)
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-89157)
PCRE2 before 10.48, on 32-bit platforms, has a pcre2_compile_32 integer overflow and resultant out-of-bounds write.(CVE-2026-89158)
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-89160)
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-89161)
Security Fix(es):
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-89156)
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-89157)
PCRE2 before 10.48, on 32-bit platforms, has a pcre2_compile_32 integer overflow and resultant out-of-bounds write.(CVE-2026-89158)
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-89160)
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-89161)
References
- https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-89156 Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-89157 Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-89158 Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-89160 Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-89161 Vendor Advisory
Internet-facing
14 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit (estimated)
- Gives an attacker full control (estimated)
Timeline
Published25 Sep 2026
Updated30 Sep 2026
First seen30 Sep 2026
Sources
OESA-2026-4111 · OSV
Track software like this
Free during beta