Socket vulnerabilities
We track 5 vulnerabilities in Socket products across 5 products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on September 13, 2026.
Latest Socket vulnerabilities
- 8.1 High severity
Socket Firewall: Improper Certificate Validation
Socket Firewall (socketdev/socket-registry-firewall) in registry mode before 2.0.0 does not verify upstream TLS certificates by default. When the api_ssl_verify and upstream_ssl_verify configuration keys are omitted from socket.yml, the generated configuration
- 7.5 High severity
Socket.IO enables bidirectional and low-latency communication for every platform.
Socket.IO enables bidirectional and low-latency communication for every platform. From 6.5.0 before 6.6.7, Engine.IO servers with WebTransport enabled can resolve a crafted session ID such as __proto__ through an inherited property of the clients object during
- 7.5 High severity
Socket.IO is an open source, real-time, bidirectional, event-based, communication framework.
Socket.IO is an open source, real-time, bidirectional, event-based, communication framework. Prior to versions 3.3.5, 3.4.4, and 4.2.6, a specially crafted Socket.IO packet can make the server wait for a large number of binary attachments and buffer them, whic
- 7.3 High severity
Socket.IO is an open source, real-time, bidirectional, event-based, communication framework.
Socket.IO is an open source, real-time, bidirectional, event-based, communication framework. A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process. This issue is fixed by commit `15af22
- 7.5 High severity
io.socket:socket.io-client: NULL Pointer Dereference
The package io.socket:socket.io-client before 2.0.1 are vulnerable to NULL Pointer Dereference when parsing a packet with with invalid payload format.