CVE-2026-126051 is a high-severity vulnerability in Node.js versions 24.x and 26.x involving a NULL pointer dereference during TLS server handshake. It occurs when certain OpenSSL callbacks are deferred but do not handle the underlying socket being destroyed before execution. An unauthenticated remote attacker can exploit this by sending a crafted client hello followed by a socket FIN, causing the server process to terminate unexpectedly due to an uncaught exception. Fixed versions are 24.22.3 and 26.13.1.
CVE-2026-123875 is a vulnerability in Node.js HTTP/2 that allows an unauthenticated client to crash the server by causing a NULL pointer dereference. This occurs when the server uses stream.respondWithFile() or stream.respondWithFD() to serve files and the client cancels the request, leading to a process abort. The issue affects Node.js versions 22.x, 24.x, and 26.x prior to their respective fixed releases.
CVE-2026-123874 is a use-after-free vulnerability in Node.js HTTP/2 affecting versions 24.x and 26.x before 24.22.3 and 26.13.1 respectively. It allows an unauthenticated client to corrupt server memory when the server uses respondWithFile() or respondWithFD() to serve files. The flaw occurs because the server may free an Http2Stream object while a write request referencing it is still queued, leading to a dereference of a freed object. This vulnerability can be exploited over both TLS and cleartext connections.
CVE-2026-123868 is a vulnerability in Node.js versions 24.x and 26.x where an unauthenticated HTTP/2 client can cause uncontrolled resource consumption. The issue arises because inbound DATA frames queued on an undrained stream are not properly accounted against the session memory budget, allowing excessive memory retention. This can lead to memory exhaustion on the server side. The vulnerability has been fixed in Node.js versions 24.22.3 and 26.13.1.
A heap-buffer-over-read vulnerability exists in the chunked-transfer-encoding HTTP request parser of the iopress server for Node.js prior to version 1.0.5. This occurs when a request declares a chunk size larger than the actual body received, causing the parser to read beyond the input buffer. The issue has been fixed in version 1.0.5.
CVE-2026-123867 is a vulnerability in Node.js versions 22.x, 24.x, and 26.x that allows a client authorized for a default hostname to bypass mutual TLS (mTLS) authorization and access a protected hostname it is not authorized for. This occurs when the server configures a per-host client certificate CA without a server certificate in the SNI context, causing the server to fallback to the default client CA. As a result, a client trusted by the default CA but not the protected CA can complete the mTLS handshake and access protected resources, while clients with the correct protected CA are rejected.
CVE-2026-123865 is a high-severity vulnerability in Node.js HTTP/2 implementation affecting versions 22.x, 24.x, and 26.x prior to specific fixed releases. An unauthenticated HTTP/2 client can cause permanent memory and file descriptor leaks by triggering protocol errors during session shutdown, leaving connections in CLOSE_WAIT state and consuming server resources indefinitely. This issue is a partial regression of a previous vulnerability (CVE-2026-48937) and has been fixed in Node.js versions 22.23.5, 24.22.3, and 26.13.1.
CVE-2026-123863 is a high-severity vulnerability in Node.js HTTP/2 implementation affecting versions 24.x and 26.x before 24.22.3 and 26.13.1 respectively. It allows an unauthenticated client to cause a server crash by triggering a reachable assertion failure during HTTP/2 session teardown. This occurs when an Http2Stream holding nghttp2-allocated header buffers outlives its session, causing a CHECK_EQ assertion failure and process termination. The vulnerability is a variant of CVE-2024-27983 and affects typical default HTTP/2 servers that respond before the request body ends.
This security update for python-Django addresses multiple vulnerabilities including potential memory exhaustion via base64-encoded file uploads, log injection through unescaped geometry form values, server-side request forgery (SSRF) via GeoJSON geometries and SpatialReference string input, and potential exposure of private data due to empty or missing Vary headers.
CVE-2026-126613 is a high-severity vulnerability in Progressive Robot Ltd's hMailServer versions 6.3.2 through 6.3.7. It involves allocation of resources without limits in the JSON reader, allowing remote attackers to exhaust server memory and hold mail delivery threads. This causes unavailability of mail delivery, the REST API, and webmail services. The vulnerability can be triggered by sending specially crafted JSON documents up to 16 MB in size, which expand in memory to about 2 GB. Attack vectors include TLS-RPT reports sent to a hosted domain's report mailbox, replies to password-protected messages when the REST API is enabled, and webmail routes. The REST API shares worker threads with SMTP, IMAP, and POP3, so multiple simultaneous attacks can exhaust system resources and disrupt all mail services. This issue is distinct from CVE-2026-107574 and affects multiple access paths.
A high-severity security vulnerability (CVE-2026-48779) affects the argo-workflows package, which uses the ws WebSocket client and server for Node.js. The vulnerability impacts versions prior to 4.1.6-r1 and 4.0.15-r2. It has a CVSS score of 7.5 with an impact on availability. Fixed versions 4.1.6-r1 and 4.0.15-r2 are available.
A high-severity security vulnerability (CVE-2026-45736) affects the argo-workflows package, specifically related to the ws library, an open source WebSocket client and server for Node.js. The vulnerability impacts versions prior to 4.1.6-r1 and 4.0.15-r2. It allows remote attackers to cause a confidentiality breach without requiring authentication or user interaction. A patch is available to address this issue.
A vulnerability in the node-forge TLS client (versions before 1.4.3) causes an uncaught TypeError when receiving a ServerHello message without an active session. This can happen after a connection close or before handshake initiation, allowing a malicious server or on-path attacker to crash the Node.js process using forge.tls. The issue is fixed in node-forge 1.4.3.
Node-forge versions from 0.1.2 up to 1.4.3 contain a vulnerability in the forge.http module where a regular expression used to trim trailing whitespace from response headers and cookies can cause excessive processing time. This can be exploited by a malicious server or on-path attacker to supply crafted response headers that block the Node.js event loop or browser tab for minutes. The issue affects applications using forge.http with a socket pool communicating with untrusted servers. There is no confidentiality or integrity impact. The vulnerability is fixed in version 1.4.3.
A vulnerability in digitalbazaar's forge (node-forge) prior to version 1.4.3 allows a malicious server or on-path attacker to cause a Node.js process to terminate unexpectedly. This occurs because the forge.tls client improperly accepts a ServerHello compression_method that it did not offer, leading to an unhandled exception when processing ServerHelloDone. The issue affects client-side usage of forge.tls but not forge.tls servers, and it does not impact confidentiality or integrity. The vulnerability is fixed in version 1.4.3.
The @tsparticles/mcp-server HTTP mode in versions prior to 4.3.1 parses incoming JSON request bodies without local error handling. A malformed JSON request causes the JSON.parse() call to throw an unhandled exception, terminating the Node.js process. This results in a denial of service until the process is externally restarted. Version 4.3.1 fixes this by returning an HTTP 400 response for invalid JSON instead of crashing.