https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 11:08:35 +0000 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1094 certfr-2026-avi-1094 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1094 https://cve.radiocsirt.org/vuln/euvd-2026-334049 EUVD-2026-334049 https://cve.radiocsirt.org/vuln/euvd-2026-334049 https://cve.radiocsirt.org/vuln/fkie_cve-2026-59724 <p>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 WebTransport upgrade handling, causing a TypeError and denial of service. This issue is fixed in version 6.6.7.</p> <p>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 WebTransport upgrade handling, causing a TypeError and denial of service. This issue is fixed in version 6.6.7.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-59724 https://cve.radiocsirt.org/vuln/ghsa-gr94-w7qr-f4j3 <p><strong>Affected:</strong> npm: engine.io</p> <p>### Impact</p> <p>Engine.IO servers with **WebTransport enabled** are vulnerable to a remotely triggerable denial of service.</p> <p>A malicious unauthenticated client can send a crafted WebTransport upgrade request containing a specially chosen session ID, such as `__proto__`. Because the session ID lookup did not properly verify that the key was an own property of the clients object, the lookup could resolve to an inherited prototype property instead of a valid Engine.IO client.</p> <p>This can cause a `TypeError` during WebTransport upgrade handling. Since the failure occurs in an asynchronous context, it may result in an unhandled Promise rejection and terminate the Node.js process on affected Node.js versions/configurations.</p> <p>Successful exploitation can allow an unauthenticated remote attacker to crash the server process and cause denial of service. Under a process supervisor, repeated exploitation may cause crash loops.</p> <p>Affected configurations are limited to deployments where WebTransport support is enabled. WebTransport is not enabled by default.</p> <p>Affected versions:</p> <p>- `engine.io &gt;= 6.5.0 &lt; 6.6.7`</p> <p>## Patches</p> <p>The issue was fixed in:</p> <p>- **engine.io 6.6.7**</p> <p>Users should upgrade to `engine.io@6.6.7` or later.</p> <p>If using Socket.IO packages that depend on Engine.IO, users should update to a Socket.IO release that includes the patched Engine.IO version.</p> <p>### Workarounds</p> <p>If upgrading immediately is not possible, affected users can mitigate the issue by disabling WebTransport support.</p> <p>WebT…</p> <p><strong>Affected:</strong> npm: engine.io</p> <p>### Impact</p> <p>Engine.IO servers with **WebTransport enabled** are vulnerable to a remotely triggerable denial of service.</p> <p>A malicious unauthenticated client can send a crafted WebTransport upgrade request containing a specially chosen session ID, such as `__proto__`. Because the session ID lookup did not properly verify that the key was an own property of the clients object, the lookup could resolve to an inherited prototype property instead of a valid Engine.IO client.</p> <p>This can cause a `TypeError` during WebTransport upgrade handling. Since the failure occurs in an asynchronous context, it may result in an unhandled Promise rejection and terminate the Node.js process on affected Node.js versions/configurations.</p> <p>Successful exploitation can allow an unauthenticated remote attacker to crash the server process and cause denial of service. Under a process supervisor, repeated exploitation may cause crash loops.</p> <p>Affected configurations are limited to deployments where WebTransport support is enabled. WebTransport is not enabled by default.</p> <p>Affected versions:</p> <p>- `engine.io &gt;= 6.5.0 &lt; 6.6.7`</p> <p>## Patches</p> <p>The issue was fixed in:</p> <p>- **engine.io 6.6.7**</p> <p>Users should upgrade to `engine.io@6.6.7` or later.</p> <p>If using Socket.IO packages that depend on Engine.IO, users should update to a Socket.IO release that includes the patched Engine.IO version.</p> <p>### Workarounds</p> <p>If upgrading immediately is not possible, affected users can mitigate the issue by disabling WebTransport support.</p> <p>WebT…</p> https://cve.radiocsirt.org/vuln/ghsa-gr94-w7qr-f4j3 https://cve.radiocsirt.org/vuln/rhsa-2026:26994 <p>dotnet: .NET: Local file tampering via link following vulnerability dotnet: ASP.NET Core: Denial of Service via uncontrolled resource consumption ws: ws: Uninitialized memory disclosure via `websocket.close()` with `TypedArray` engine.io: Engine.IO: Denial of Service via crafted WebTransport session ID js-yaml: js-yaml: Denial of Service via quadratic CPU time parsing with merge keys js-yaml: js-yaml: Denial of Service via crafted YAML ordered-map document</p> <p>dotnet: .NET: Local file tampering via link following vulnerability dotnet: ASP.NET Core: Denial of Service via uncontrolled resource consumption ws: ws: Uninitialized memory disclosure via `websocket.close()` with `TypedArray` engine.io: Engine.IO: Denial of Service via crafted WebTransport session ID js-yaml: js-yaml: Denial of Service via quadratic CPU time parsing with merge keys js-yaml: js-yaml: Denial of Service via crafted YAML ordered-map document</p> https://cve.radiocsirt.org/vuln/rhsa-2026:26994