CVE-2026-89162
Received Received - Intake

PCRE2 Memory Disclosure in Serialization

Vulnerability report for CVE-2026-89162, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-11

Last updated on: 2026-09-11

Assigner: MITRE

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-11
Last Modified
2026-09-11
Generated
2026-09-11
AI Q&A
2026-09-11
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
pcre2project pcre2 to 10.48 (exc)
pcre2project pcre2 10.48

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-669 The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere, in a manner that provides unintended control over that resource.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-89162 is a low-severity vulnerability in PCRE2 versions 10.45 and earlier. It involves an uninitialized memory disclosure in the pcre2_serialize_encode() function, where two bytes of uninitialized data from previous memory allocations may be exposed when serializing certain compiled regular expressions. This happens due to uninitialized memory in compiled structures for specific regex patterns and compile options, such as character classes with Unicode code points.

Detection Guidance

To detect this vulnerability, check the installed version of PCRE2 on your system. Run: pcre2-config --version or pkg-config --modversion libpcre2-8. If the version is 10.45 or earlier, the system is vulnerable.

Impact Analysis

The impact is limited to the disclosure of two random bytes of memory. If serialized data containing these bytes is exposed to untrusted actors, it could potentially leak sensitive information. However, the vulnerability requires local access and has high attack complexity, making exploitation unlikely in most scenarios.

Compliance Impact

This vulnerability involves disclosure of two uninitialized memory bytes in PCRE2's pcre2_serialize_encode function, which could potentially expose sensitive data if serialized regex patterns are accessed by untrusted parties. While the impact is limited to two random bytes, it may pose compliance risks under GDPR or HIPAA if such data exposure occurs in systems handling personal or health information.

Mitigation Strategies

Upgrade PCRE2 to version 10.48 or later immediately. For Linux systems, use your package manager (e.g., apt upgrade libpcre2-8-0 or yum update pcre2). For source builds, download and compile the latest version from the official PCRE2 repository.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-89162. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart