Security: When the try_files directive with values containing variables was used in a location with the alias directive, a buffer overflow might occur in certain configurations, allowing an attacker to corrupt the worker process memory or cause its crash (CVE-2026-125283); the fix was ported from nginx 1.31.9.
Security: When HTTP/2 was used, processing of specially crafted messages from a client while a response was being sent to it might result in worker process memory corruption or a worker process crash, or might have potential other impact (CVE-2026-123007); the fix was ported from nginx 1.31.9.
Security: When HTTP/2 was used, if processing a request required an outgoing connection (for example, to a proxied server) and free connections (the worker_connections directive) were not enough, an HTTP/2 connection could be mistakenly closed while a request was still being processed in it; as a result, worker process memory corruption or a worker process crash could occur (CVE-2026-123633); the fix was ported from nginx 1.31.9.
Security: When HTTP/3 was used, if processing a request required an outgoing connection (for example, to a proxied server) and free connections (the worker_connections directive) were not enough, a QUIC connection could be mistakenly closed while a request was still being processed in it; as a result, worker process memory corruption or a worker process crash could occur (CVE-2026-121810); the fix was ported from nginx 1.31.9.
Security: When the resolver directive was used to resolve proxied server names while processing a request, and the same name was simultaneously resolved in a subrequest, an attacker able to trigger name resolution might corrupt worker process memory or cause a worker process crash; the issue might also have potential other impact (CVE-2026-123634); the fix was ported from nginx 1.31.9.
Security: In the mail Proxy module, closing the connection or writing data by a client while the server was connecting to a proxied server (the proxy on directive), resolving a client name, or waiting for a response from the authentication server (the auth_http directive) could lead to worker process memory corruption or a worker process crash (CVE-2026-113425); the fix was ported from nginx 1.31.9.
Security: In the stream module, if virtual servers were selected by SNI and client SSL certificate verification (the ssl_verify_client, ssl_client_certificate and ssl_trusted_certificate directives) was configured more strictly in the server selected by SNI than in the default server, the verification could be performed using the configuration of the default server, allowing an attacker to bypass it (CVE-2026-120967); the fix was ported from nginx 1.31.9.
Security: When the ssl_preread directive was used, malformed ClientHello messages might be interpreted differently than in other TLS implementations, which might result in bypassing security restrictions based on the $ssl_preread_server_name and $ssl_preread_alpn_protocols variables (CVE-2026-123640); the fix was ported from nginx 1.31.9.
Security: While proxying over HTTP/3 (proxy_http_version 3), when evaluating string expressions with unnamed capture variables ($1, $2, etc.) in the proxy_set_header and proxy_set_body directives together with a variable defined by the map directive whose value is determined by a regular expression, memory corruption or a crash of a worker process could occur. Thanks to Iaroslav Makarov for the vulnerability report.