{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-112085", "assignerOrgId": "ce714d77-add3-4f53-aff5-83d477b104bb", "state": "PUBLISHED", "assignerShortName": "openjs", "dateReserved": "2026-10-18T15:33:43.925Z", "datePublished": "2026-10-22T09:31:59.124Z", "dateUpdated": "2026-10-22T09:31:59.124Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "ce714d77-add3-4f53-aff5-83d477b104bb", "shortName": "openjs", "dateUpdated": "2026-10-22T09:31:59.124Z"}, "descriptions": [{"lang": "en", "value": "webpack-dev-server is a development server that provides live reloading for webpack projects. In versions before 5.2.7 and in version 6.0.0, when a proxy entry is configured to forward WebSockets, the server forwards non-HMR WebSocket upgrade requests to the proxy target without validating the Host or Origin headers, so the allowedHosts protection does not apply to those proxied upgrades. A malicious web page visited by a developer can open a cross-origin WebSocket through the dev server and read from and write to the proxied backend, even when the server is bound to loopback. The issue is fixed in webpack-dev-server 5.2.7 and 6.1.0, where proxied WebSocket upgrades pass the same Host and Origin validation as the HMR WebSocket, and users should upgrade to one of those versions or later. As a workaround, omit WebSocket forwarding from proxy entries that do not need it and scope the proxy to specific paths.", "supportingMedia": [{"type": "text/html", "base64": false, "value": "webpack-dev-server is a development server that provides live reloading for webpack projects. In versions before 5.2.7 and in version 6.0.0, when a proxy entry is configured to forward WebSockets, the server forwards non-HMR WebSocket upgrade requests to the proxy target without validating the Host or Origin headers, so the allowedHosts protection does not apply to those proxied upgrades. A malicious web page visited by a developer can open a cross-origin WebSocket through the dev server and read from and write to the proxied backend, even when the server is bound to loopback. The issue is fixed in webpack-dev-server 5.2.7 and 6.1.0, where proxied WebSocket upgrades pass the same Host and Origin validation as the HMR WebSocket, and users should upgrade to one of those versions or later. As a workaround, omit WebSocket forwarding from proxy entries that do not need it and scope the proxy to specific paths."}]}], "affected": [{"vendor": "webpack-dev-server", "product": "webpack-dev-server", "defaultStatus": "unaffected", "versions": [{"versionType": "semver", "status": "affected", "version": "0", "lessThan": "5.2.7"}, {"versionType": "semver", "status": "unaffected", "version": "5.2.7"}, {"versionType": "semver", "status": "affected", "version": "6.0.0", "lessThan": "6.1.0"}, {"versionType": "semver", "status": "unaffected", "version": "6.1.0"}], "packageURL": "pkg:npm/webpack-dev-server"}], "references": [{"url": "https://github.com/webpack/webpack-dev-server/security/advisories/GHSA-cfqc-fj3v-j925"}, {"url": "https://cna.openjsf.org/security-advisories.html"}], "credits": [{"lang": "en", "type": "reporter", "value": "euriconicacio"}, {"lang": "en", "type": "remediation developer", "value": "UlisesGascon"}, {"lang": "en", "type": "coordinator", "value": "bjohansebas"}, {"lang": "en", "type": "remediation reviewer", "value": "alexander-akait"}], "title": "webpack-dev-server vulnerable to cross-origin WebSocket access via proxied upgrades", "metrics": [{"format": "CVSS", "cvssV3_1": {"version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N", "baseScore": 8.2, "baseSeverity": "HIGH"}, "scenarios": [{"lang": "en", "value": "GENERAL"}]}], "problemTypes": [{"descriptions": [{"cweId": "CWE-346", "lang": "en", "description": "CWE-346: Origin Validation Error", "type": "CWE"}]}, {"descriptions": [{"cweId": "CWE-1385", "lang": "en", "description": "CWE-1385: Missing Origin Validation in WebSockets", "type": "CWE"}]}], "x_generator": {"engine": "cve-kit 1.0.0"}}}}

{}

{}

{}

{}