This page was not yet optimized for use on mobile devices.
CVE-2026-48779
Data
| Vulnerability ID | CVE-2026-48779 |
|---|---|
| Published on | 17.06.2026 13:20 |
| Severity | HIGH |
Vulnerable configurations
-
cpe:2.3:a:ws_project:ws:1.1.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:ws_project:ws:1.1.1:*:*:*:*:node.js:*:*,
cpe:2.3:a:ws_project:ws:1.1.2:*:*:*:*:node.js:*:*,
cpe:2.3:a:ws_project:ws:1.1.3:*:*:*:*:node.js:*:*,
cpe:2.3:a:ws_project:ws:1.1.4:*:*:*:*:node.js:*:*,
cpe:2.3:a:ws_project:ws:1.1.5:*:*:*:*:node.js:*:*,
cpe:2.3:a:ws_project:ws:2.0.0:-:*:*:*:node.js:*:*,
cpe:2.3:a:ws_project:ws:2.0.0:beta0:*:*:*:node.js:*:*,
cpe:2.3:a:ws_project:ws:2.0.0:beta1:*:*:*:node.js:*:*,
cpe:2.3:a:ws_project:ws:2.0.0:beta2:*:*:*:node.js:*:*,
…
Vulnerable certificates
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.