CVE-2026-103111VulnerabilityPublished 30 Sep 2026Updated 3 Nov 2026

PCRE2 before 10.49, when there is an attacker-controlled regular expression and certain JIT API usage, allows an

Affects pcre2Source GCVE Database

Compare

Authoritative record:CVE-2026-103111· High 7.6

Not known to be exploited · CVSS 7.6 High · fixed in 10.49 : patch pcre2 soon.

Data as of 3 Nov 2026, 22:58 UTC

CVSS 3.1 base score

7.6High

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 10.49

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: High
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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 30 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–
Ubuntu Pro 18.04 LTSpcre2`pkg:deb/ubuntu/pcre2?arch=source&distro=esm-apps/bionic`Other threats	Affected 10.22-3 – 10.31-2ubuntu0.1~esm2 7 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

A fix is available in PCRE2 version 10.49 and later. Users should upgrade to version 10.49 or newer to remediate this vulnerability. No additional mitigation steps are indicated or required beyond applying the official patch.

Description

PCRE2 versions before 10.49 contain a vulnerability where an attacker-controlled regular expression combined with certain JIT API usage can cause an out-of-bounds write with arbitrary data. This flaw can lead to integrity and availability impacts. The vulnerability has a high severity score of 7.6 CVSS v3.1. Multiple specific versions of PCRE2 are affected. No public exploits or known in-the-wild exploitation have been reported as of the publication date.

Impact

The vulnerability allows an attacker to perform an out-of-bounds write with arbitrary data, which can compromise the integrity of the affected system and potentially cause application crashes or instability. Confidentiality impact is limited, but integrity impact is high and availability impact is low. Exploitation requires control over the regular expression and specific JIT API usage, with low complexity and privileges needed.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2026, 21:49 UTC

Technical details

References

Community reviews

Related threats