2.9Low
Pcre Pcre2
CVE-2026-89162
In PCRE2 before 10.48, pcre2_serialize_encode might disclose two bytes to an adversary, typically in a situation where the access available to the adversary is already unsafe.
What this means for your business
- It affects Pcre2. It matters if your company, or a supplier that handles your data, runs it.
- Code showing how to exploit it has been published, but real attacks have not been confirmed.
- An attacker can use it only with access to the machine itself, without a login, and without anyone at your company clicking anything.
What to do
- 1Check whether your company or your suppliers run Pcre2, and which version. The affected versions are listed further down this page.
- 2If you do, apply the vendor's fix. A patch or vendor advisory has been published.
Not sure if your company is exposed?
Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.
Scoring
- CVSS
- 2.9 (v3.1)
- Vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N- Weakness
- CWE-669
- Assigned by
- cve@mitre.org
Dates
- Published
- 2026-09-11
- Last modified
- 2026-09-16
- Sources
- NVD
Affected products
- Pcre Pcre210.45 - 10.48, 10.48
As listed in the NVD configuration data. Not a statement about your estate.