Ws Project

    Dashboard / Vendors

    Products: 1
    Vulnerabilities: 5
    Known Exploited: 0
    0
    Critical Level Threats
    3
    High Level Threats
    2
    Medium Level Threats
    0
    Low Level Threats

    Vulnerabilities

    100806040200
    JanFebMarAprMayJunJulAugSepOctNovDec
    Critical Level Threats
    High Level Threats
    Medium Level Threats
    Low Level Threats

    Products Security index

    Actions
    Items Per Page

    Vulnerabilities

    CVE-2026-48779

    ws: Memory exhaustion DoS from tiny fragments and data chunks

    Last Modified: Aug 28, 2026
    Published: Jun 16, 2026

    CVE-2026-45736

    ws: Uninitialized memory disclosure

    Last Modified: Aug 28, 2026
    Published: May 15, 2026

    CVE-2021-32640

    ReDoS in Sec-Websocket-Protocol header

    Last Modified: Nov 21, 2024
    Published: May 25, 2021

    CVE-2016-10518

    A vulnerability was found in the ping functionality of the ws module before 1.0.0 which allowed clients to allocate memory by sending a ping frame. The ping functionality by default responds with a pong frame and the previously given payload of the ping frame. This is exactly what you expect, but internally ws always transforms all data that we need to send to a Buffer instance and that is where the vulnerability existed. ws didn't do any checks for the type of data it was sending. With buffers in node when you allocate it when a number instead of a string it will allocate the amount of bytes.

    Last Modified: Nov 21, 2024
    Published: May 31, 2018

    CVE-2016-10542

    ws is a "simple to use, blazing fast and thoroughly tested websocket client, server and console for node.js, up-to-date against RFC-6455". By sending an overly long websocket payload to a `ws` server, it is possible to crash the node process. This affects ws 1.1.0 and earlier.

    Last Modified: Nov 21, 2024
    Published: May 31, 2018
    Items Per Page