Skip to main content

webpack-dev-server EUVDEUVD-2026-108109

| CVE-2026-114348 MEDIUM
Error Message Information Leak (CWE-209)
2026-10-22 openjs
5.3
CVSS 3.1 · Vendor: openjs
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach dev server over network
  2. Exploit
    Send request with malformed Host (file:badport)
  3. Execution
    Bypass Host/allowedHosts validation, URL construction throws
  4. Impact
    Receive 500 stack trace disclosing filesystem paths and module locations

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Error message sanitization
MITRE ATT&CK

1 technique across 1 tactic: Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires that the webpack-dev-server /webpack-dev-server/open-editor endpoint (registered unauthenticated by default) be network-reachable by the attacker, and that the server run in its default non-production mode, which returns full exception stack traces in HTTP 500 bodies. The concrete trigger is a request whose Host header begins with 'file:' or '<something>-extension:' (e.g. 'file:badport'), which short-circuits the Origin-scheme regex before the hostname and allowedHosts checks run. Limiting factors: this is a development server, so exploitation requires the dev server to be bound beyond localhost (reachable by a network peer); configurations running in production mode would not emit the stack-trace body; affected versions are 5.1.0-5.2.6 and 6.0.0 only.

Impact

This is a genuinely moderate issue whose signals are internally consistent: CVSS 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) describes a network-reachable, low-complexity, unauthenticated flaw with confidentiality-only impact (C:L, I:N, A:N), which matches CWE-209 (information exposure through an error message). The vuln.today Decision label is 'this_month' - a patch-this-cycle priority, not act_now or emergency - and that aligns with the limited impact: the advisory confirms there is no denial of service and no code execution, only disclosure of absolute filesystem paths, installed module locations, and source line numbers via a 500 stack trace. No EPSS score, no CISA KEV listing, and no SSVC/automatable fields were supplied, and no proof-of-concept or exploit reference appears in the input, so exploitation probability cannot be quantified from the data. Note the tension between the metadata and the primary source: the input Tags include 'Denial Of Service', but the GHSA advisory and the CVE description both state explicitly that the server keeps running and there is no DoS - treat the DoS tag as incorrect. The practical risk is further bounded by exposure: webpack-dev-server is a development tool, so real risk depends on whether the dev server is reachable beyond localhost. This is a real priority to patch but not a high-urgency, widely-weaponized threat.

Exploit ScenarioDerived

A development server is reachable by another host on the local or corporate network (not bound solely to loopback). The attacker sends an unauthenticated HTTP request to /webpack-dev-server/open-editor with a malformed Host header such as 'file:badport'; the Origin-style regex short-circuits the hostname and allowedHosts checks, URL construction then throws, and the default non-production error handler returns a 500 whose body leaks absolute filesystem paths, installed module locations, and internal source line numbers for reconnaissance. No public exploit was identified in the provided data, and low attack complexity (AC:L) means no special timing or grooming is needed.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 22, 2026

Information disclosure in webpack-dev-server 5.1.0 through 5.2.6 and 6.0.0 lets an unauthenticated network peer reach the unauthenticated /webpack-dev-server/open-editor endpoint and bypass Host validation with a malformed Host such as 'file:badport', causing URL construction to throw. In the default non-production mode the resulting HTTP 500 includes the full exception stack trace, exposing absolute filesystem paths, installed module locations, and internal source line numbers; the server stays up, so there is no denial of service. Exploitation requires the dev server to be network-reachable, and no public exploit was identified at time of analysis.

RemediationAI

Vendor-released patch: upgrade to webpack-dev-server 5.2.7 or 6.1.0, or later, on the affected branches. The advisory states there are no workarounds, so upgrading is the complete fix. Advisory: https://github.com/webpack/webpack-dev-server/security/advisories/GHSA-wqhc-fvfg-56q6.

Affected VersionsENISA

webpack-dev-server 6.0.0 <6.1.0
webpack-dev-server 5.1.0 <5.2.7

Affected Packages

euvd webpack_dev_server fix: 5.2.7, 6.1.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

webpack-dev-server is a development server that provides live reloading for webpack projects. The open-editor endpoint is registered without authentication and relies on a Host-validation routine whose regular expression is intended for browser Origin schemes. A Host value beginning with 'file:' or '<something>-extension:' short-circuits validation before the hostname and allowedHosts checks run, so a request such as Host: file:badport reaches the endpoint's URL construction and throws. In default non-production mode the server returns an HTTP 500 body with the full exception stack trace, creating CWE-209 information exposure; the advisory also associates CWE-1289 with the validation bypass. The flaw is confined to the stated versions and requires network reachability to the dev server; it does not cause denial of service.

Know when Webpack Dev Server gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (openjs) PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
vuln.today AI 5.3 MEDIUM

Unauthenticated network request with a simple malformed Host (AV:N/AC:L/PR:N/UI:N); only low confidentiality impact from leaked paths/stack trace, no integrity, availability, or scope change.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Red Hat 5.3 MEDIUM

Primary rating from Vendor (openjs).

CVSS VectorVendor: openjs

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

Lifecycle Timeline

2
Patch available
Oct 22, 2026 - 11:16 EUVD
CVE Published
Oct 22, 2026 - 09:38 cve.org
MEDIUM 5.3

DescriptionCVE.org

webpack-dev-server is a development server that provides live reloading for webpack projects. In versions from 5.1.0 before 5.2.7 and in version 6.0.0, the unauthenticated open-editor endpoint validates the Host header with a regular expression meant for browser Origin schemes, so a Host value beginning with file: or with an extension scheme short-circuits the hostname and allowedHosts checks. A network peer that can reach the dev server can send a request with a malformed Host that passes validation and then causes the endpoint's URL construction to throw, and in the default non-production mode the server returns an HTTP 500 body containing the full exception stack trace, which discloses absolute filesystem paths, installed module locations, and internal source line numbers. The server keeps running, so there is no denial of service. The issue is fixed in webpack-dev-server 5.2.7 and 6.1.0, and users should upgrade to one of those versions or later.

Threat Intelligence Overview

EPSS Score
0.3%
Top 73% exploitable
Prevalence
High
extremely common frontend build tooling, but runs on dev machines not production
Social Media
1
Sightings
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment Vendor CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
High
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy