VulnerabilityPublished 29 Oct 2026

CVE-2026-95114: libwebsockets security update

Affects libwebsocketsSource GCVE Database

Compare

Mentioned vulnerabilities

CVE-2026-95115

Authoritative record:CVE-2026-95114· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 4.3.0-12.oe2203sp4 soon.

Data as of 29 Oct 2026, 10:49 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.3.0-12.oe2203sp4

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

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

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: 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: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Oct 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 29 Oct 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

Upgrade libwebsockets to 4.3.0-12.oe2203sp4.

Affected software

Product	Affected	Fixed in
openEuler 22.03-LTS-SP4libwebsockets`pkg:rpm/openEuler/libwebsockets&distro=openEuler-22.03-LTS-SP4`Other threats	Affected <4.3.0-12.oe2203sp4	Fixed in 4.3.0-12.oe2203sp4

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 libwebsockets to version 4.3.0-12.oe2203sp4 or later, where this vulnerability has been fixed. Applying this official patch fully mitigates the risk of denial of service from this issue.

Description

Libwebsockets versions prior to 4.3.0-12.oe2203sp4 contain an out-of-bounds read vulnerability in the LEJP incremental parser that can be exploited remotely to cause a denial of service. This vulnerability is identified as CVE-2026-95114 and is rated high severity with a CVSS score of 7.5. A patch is available in version 4.3.0-12.oe2203sp4 that addresses this issue.

Impact

Successful exploitation of CVE-2026-95114 results in a denial of service condition, causing the affected application using libwebsockets to crash or become unresponsive. There is no impact on confidentiality or integrity reported. The vulnerability can be triggered remotely without authentication.

Summary

Libwebsockets, a lightweight C library for network protocols, has an out-of-bounds read vulnerability in its LEJP incremental parser component (lib/misc/lejp.c). This flaw allows remote attackers to cause a denial of service by triggering the parser to read beyond allocated memory bounds. The vulnerability is tracked as CVE-2026-95114. A related buffer overflow vulnerability (CVE-2026-95115) also exists in the same parser but is distinct. The vulnerability affects versions before 4.3.0-12.oe2203sp4, where it has been fixed.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 10:49 UTC

Technical details

References

Community reviews

Related threats