CVE-2026-112085VulnerabilityPublished 22 Oct 2026Updated 28 Oct 2026

Node webpack:

Affects node-webpackSource GCVE Database

Authoritative record:CVE-2026-112085· High 8.2

Not known to be exploited · CVSS 8.2 High · fixed in 5.2.7 : patch node-webpack soon.

Data as of 28 Oct 2026, 23:13 UTC

CVSS 3.1 base score

8.2High

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

Patch: Available – fixed in 5.2.7

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

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

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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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.10node-webpack`pkg:deb/ubuntu/node-webpack?arch=source&distro=stonking`Other threats	Affected =5.105.4+dfsg1+~cs15.13.23-2 =5.108.0+dfsg1+~cs14.7.20-2	Fixed in–
Ubuntu 26.04 LTSnode-webpack`pkg:deb/ubuntu/node-webpack?arch=source&distro=resolute`Other threats	Affected =5.97.1+dfsg1+~cs11.18.27-3 =5.97.1+dfsg1+~cs11.18.27-4 =5.105.4+dfsg1+~cs15.13.23-2	Fixed in–
Ubuntu 24.04 LTSnode-webpack`pkg:deb/ubuntu/node-webpack?arch=source&distro=noble`Other threats	Affected =5.76.1+dfsg1+~cs17.16.16-1	Fixed in–
Ubuntu 22.04 LTSnode-webpack`pkg:deb/ubuntu/node-webpack?arch=source&distro=jammy`Other threats	Affected =4.43.0-6build4 =4.43.0-7	Fixed in–
Ubuntu 20.04 LTSnode-webpack`pkg:deb/ubuntu/node-webpack?arch=source&distro=focal`Other threats	Affected =4.7.0-3 =4.30.0-7 =4.30.0-9	Fixed in–
Ubuntu 18.04 LTSnode-webpack`pkg:deb/ubuntu/node-webpack?arch=source&distro=bionic`Other threats	Affected =3.5.6-1build3 =3.5.6-1build4 =3.5.6-2	Fixed in–

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

AI-suggested

Upgrade webpack-dev-server to version 5.2.7 or later, or 6.1.0 or later, where the vulnerability is fixed by proper Host and Origin header validation on proxied WebSocket upgrades. As a temporary workaround, avoid forwarding WebSocket connections in proxy entries that do not require it and restrict proxying to specific paths to reduce exposure.

Description

In webpack-dev-server versions before 5.2.7 and version 6.0.0, a vulnerability exists in the proxy WebSocket forwarding feature. The server forwards non-HMR WebSocket upgrade requests to the proxy target without validating Host or Origin headers, bypassing allowedHosts protections. This allows a malicious web page visited by a developer to open a cross-origin WebSocket through the dev server and interact with the proxied backend, even if the server is bound to loopback. The issue is fixed in versions 5.2.7 and 6.1.0.

Impact

This vulnerability allows an attacker controlling a malicious web page visited by a developer to establish unauthorized cross-origin WebSocket connections through the webpack-dev-server to backend services. This can lead to unauthorized data access (confidentiality impact) and limited unauthorized modification (integrity impact) of the proxied backend. The server's allowedHosts protection is bypassed for these WebSocket upgrades, increasing the attack surface even when the server is bound to loopback. There is no impact on availability reported.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 23:13 UTC

Technical details

References

Community reviews

Related threats