@hono/node-server allows running the Hono application on Node.js. Prior to 1.19.18 and from 2.0.0 until 2.1.6, the server passes a raw request-target containing a backslash in its path to the WHATWG URL parser, which treats the backslash as a path separator and resolves dot segments. A reverse proxy, load balancer, or web application firewall that preserves the backslash and applies path-based rules to the original request can therefore permit a request that the application normalizes to a blocked route. This lets an unauthenticated client reach route content that the upstream component was intended to deny, while Hono application access controls are unaffected because they operate on the normalized path. This issue is fixed in versions 1.19.18 and 2.1.6.
pgEdge Postgres MCP Server enables SQL queries against PostgreSQL databases through Model Context Protocol compatible clients. Prior to 1.1.0, custom pl-do tools interpolated JSON arguments into a PostgreSQL DO block delimited by fixed dollar-quote tags. An argument containing $mcp_custom_tool$ could terminate the block and inject arbitrary SQL statements, while $mcp_args$ could inject procedural code into a plpgsql block. Because the statement used the simple query protocol, injected text could include additional statements and transaction control, bypassing read_only and accessing data or modifying resources available to the connecting role. The issue requires at least one pl-do custom tool; sql and pl-func tools pass arguments as bind parameters and are not affected by this injection mechanism. This issue is fixed in 1.1.0.
A validation flaw in the DNS SRV host discovery of the MongoDB Node.js driver may cause the driver to connect to a host outside the expected domain. For a mongodb+srv:// connection string, the driver checks each host name in the DNS SRV response against the domain of the connection string. The driver then builds the connection address from the original name, in which certain characters end the host name early. An unauthenticated party who can forge or change the DNS SRV response may redirect the connection to a host of their choice. TLS does not prevent this, because the driver verifies the server certificate against the redirected host name. This may result in unintended disclosure of application data and authentication credentials, and in altered query results. Applications that use mongodb:// connection strings are not affected.
The buffer-code-exercise-api RubyGem version 1.0.1 contains malicious code embedded in a file declared as a native extension. During gem installation, this code executes and collects sensitive system information including hostname, login name, current working directory, home directory, and contents of system files such as /etc/passwd, /etc/hosts, and /etc/resolv.conf. It then encodes this data in JSON and sends it over TLS to a hardcoded external server unrelated to the package publisher. This behavior is indicative of data exfiltration via an install-time execution vector.
Multiple vulnerabilities have been fixed in Node.js versions 22.x, 24.x, and 26.x. These include issues in the HTTP/2 implementation, HTTPS server module, TLS handling, and proxy error handling. The vulnerabilities cover a range of weaknesses such as use-after-free, improper handling of errors, and security misconfigurations.
The MISP Modules website component contains an information disclosure vulnerability in the external tools management interface. The /external_tools/list endpoint returned stored API keys (the api_key field) in its JSON response via the ExternalTools model serializer. Additionally, the browser-based edit form pre-populated the API key input field with the stored credential value, exposing it in the DOM.
The /external_tools/list endpoint is accessible without authentication (the regression tests verify the response for both authenticated and unauthenticated clients), meaning any network-reachable client could retrieve the API keys for all configured external tools. These keys are used by the server to authenticate submissions to external analysis or enrichment services, so their disclosure allows an attacker to impersonate the MISP instance or directly access those external services.
The vulnerability also affected the edit workflow: the change_config endpoint previously required the API key to be present and non-empty on every save, forcing the key to round-trip through the client. The browser JavaScript stored the key in a reactive state object and updated the in-memory tool list with the credential value, further increasing the window of exposure in client-side memory and network traffic.
Affected component: the website sub-application of MISP Modules, specifically the external_tools module (serializer in models.py, list endpoint, and the external_tools_index.html template). The impact is limited to confidentiality of the stored API keys; no integrity or availability impact on the MISP Modules website itself is indicated by the patch.
A security advisory from Red Hat addresses multiple vulnerabilities in Red Hat Hardened Images RPMs, including a notable flaw in Node.js (CVE-2026-123872). This Node.js vulnerability allows an authenticated remote attacker to bypass client certificate authentication policies by renegotiating TLS 1.2 connections and changing the target server name, potentially gaining unauthorized access to restricted endpoints. The issue affects deployments where Node.js directly handles TLS termination with heterogeneous mutual TLS policies using TLS 1.2. Enforcing TLS 1.3 or terminating TLS at a proxy that does not forward TLS 1.2 renegotiation mitigates the risk. The advisory includes updates to various nodejs24 RPM packages to address these issues.
A vulnerability in Node.js allows a client authorized for the default hostname to bypass per-host mutual TLS (mTLS) authorization and access a protected hostname it is not authorized for. This occurs when a TLS server configures a hostname with a client-certificate CA but no server certificate, causing the client CA to fall back to the default. As a result, a client trusted by the default CA can complete mTLS to the protected hostname despite lacking proper authorization. This affects Node.js versions 22.x, 24.x, and 26.x.
A use-after-free vulnerability exists in Node.js HTTP/2 when serving files using respondWithFile() or respondWithFD(). An unauthenticated client can cause the server to free an Http2Stream object while a write operation referencing it is still queued, leading to a dereference of freed memory. This affects Node.js versions 26.x starting from 26.9.0 and 24.x starting from 24.22.0. The vulnerability can be triggered over both TLS and cleartext connections.
A NULL pointer dereference vulnerability in Node.js HTTP/2 allows an unauthenticated client to crash the server by cancelling file downloads. This affects Node.js versions 22.x, 24.x, and 26.x. The issue occurs when the server uses stream.respondWithFile() or stream.respondWithFD() to serve files, and the client cancels the request, causing a StreamPipe to be torn down improperly and leading to a NULL pointer dereference that aborts the process. No special crafted frames are required to trigger the crash.
A use-after-destroy vulnerability exists in Node.js TLS server handshake handling when using certain OpenSSL callbacks. This flaw allows a remote, unauthenticated attacker to cause the Node.js server process to terminate unexpectedly by sending a specially crafted client hello message followed by a socket FIN. The issue affects Node.js versions 24.x and 26.x and results in an uncaught exception that crashes the server process.
An unauthenticated HTTP/2 client can cause a Node.js server to leak memory and file descriptors indefinitely by triggering a protocol error during session shutdown. This leaves sockets in CLOSE_WAIT state and HTTP/2 session state held in memory without release. The issue affects Node.js versions 22.x, 24.x, and 26.x and is a partial regression of a previous fix (CVE-2026-48937).
CVE-2026-123868 is a vulnerability in Node.js versions 24.x and 26.x where an unauthenticated HTTP/2 client can exhaust server memory. 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 denial of service by exhausting server resources.
A reachable assertion vulnerability in Node.js HTTP/2 session teardown allows any unauthenticated client to abort the server process. This occurs because an Http2Stream holding nghttp2-allocated header buffers can outlive its session, causing a failed assertion during session destruction. The issue affects Node.js versions 26.x (since 26.9.0) and 24.x (since 24.22.0) and is a variant of a previously fixed vulnerability (CVE-2024-27983).
Laradocs versions from 0.4.0 up to but not including 1.0.0 contain a local OS command injection vulnerability in server-side KaTeX rendering. This occurs due to an unescaped Node.js binary path used in a proc_open() command string. The vulnerability is fixed in version 1.0.0.