VulnerabilityPublished 11 Sep 2026Updated 3 Nov 2026

CVE-2026-89160: PCRE2 before 10.48 has a pcre2_match out-of-bounds read during the PCRE2_MATCH_INVALID_UTF matching

Affects pcre2Source GCVE Database

Compare

Authoritative record:CVE-2026-89160· Low 3.7

Not known to be exploited · CVSS 3.7 Low.

Data as of 3 Nov 2026, 23:35 UTC

CVSS 3.1 base score

3.7Low

How severe the flaw is on the 0–10 CVSS scale.

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10pcre2`pkg:deb/ubuntu/pcre2?arch=source&distro=stonking`Other threats	Affected =10.46-1build1 =10.46-1ubuntu1	Fixed in–
Ubuntu 26.04 LTSpcre2`pkg:deb/ubuntu/pcre2?arch=source&distro=resolute`Other threats	Affected =10.46-1 =10.46-1build1 =10.46-1ubuntu0.1	Fixed in–
Ubuntu 24.04 LTSpcre2`pkg:deb/ubuntu/pcre2?arch=source&distro=noble`Other threats	Affected 10.42-4 – 10.42-4ubuntu2.2 5 affected builds	Fixed in–
Ubuntu 22.04 LTSpcre2`pkg:deb/ubuntu/pcre2?arch=source&distro=jammy`Other threats	Affected 10.37-0ubuntu2 – 10.39-3ubuntu0.2 5 affected builds	Fixed in–
Ubuntu Pro 20.04 LTSpcre2`pkg:deb/ubuntu/pcre2?arch=source&distro=esm-infra/focal`Other threats	Affected 10.32-5 – 10.34-7ubuntu0.1+esm1 4 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade to PCRE2 version 10.48 or later where this vulnerability is fixed. Since the affected versions are explicitly listed, applying the official update from the vendor or distribution maintainers is recommended. No other mitigations or workarounds are documented.

Description

PCRE2 versions before 10.48 contain a vulnerability where the pcre2_match function performs an out-of-bounds read when processing an invalid UTF subject with the PCRE2_MATCH_INVALID_UTF flag. This flaw can lead to information disclosure and potential application instability.

Impact

An attacker can cause the pcre2_match function to read memory beyond the intended buffer when processing invalid UTF input, potentially leading to information disclosure (confidentiality impact) and application crashes (availability impact). There is no indication of privilege escalation or integrity impact. The vulnerability is remotely exploitable without authentication and requires low attack complexity.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2026, 23:35 UTC

Technical details

References

Community reviews

Related threats