From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] nginx: Update to version 1.31.9
Date: Thu, 19 Nov 2026 14:55:10 +0100 [thread overview]
Message-ID: <20261119135512.3276857-5-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20261119135512.3276857-1-adolf.belka@ipfire.org>
- Update from version 1.29.1 to 1.31.9
- No change in rootfile
- 36 CVE fixes in total over 9 versions
10 in 1.31.9
5 in 1.31.7
1 in 1.31.6
3 in 1.31.3
3 in 1.31.2
1 in 1.31.1
6 in 1.31.0
6 in 1.29.7
1 in 1.29.5
- Changelog
1.31.9
*) Security: a buffer overflow might occur in a worker process when
using the "try_files" and "alias" directives in certain
configurations (CVE-2026-125283).
*) Security: a flow control window overflow in HTTP/2 might allow an
attacker to cause a segmentation fault in a worker process, or might
have potential other impact (CVE-2026-123007).
*) Security: use-after-free might occur in a worker process when using
HTTP/2 if worker_connections were not enough (CVE-2026-123633).
*) Security: use-after-free might occur in a worker process when using
HTTP/3 if worker_connections were not enough (CVE-2026-121810).
*) Security: use-after-free condition might occur if the "resolver"
directive was used and the same name was simultaneously resolved in
subrequests, allowing an attacker who is able to trigger name
resolution to cause segmentation fault in a worker process, or might
have potential other impact (CVE-2026-123634).
*) Security: use-after-free might occur in a worker process in the mail
proxy server (CVE-2026-113425).
*) Security: in the stream module, an attacker who is able to complete
the SSL handshake synchronously might cause client SSL certificates
to be verified using the configuration of the default server rather
than the virtual server selected by SNI (CVE-2026-120967).
*) Security: a segmentation fault might occur in a worker process when
using PROXY protocol version 2 with dynamic SSL certificate loading
(CVE-2026-120993).
*) Security: the ngx_stream_ssl_preread_module might interpret malformed
ClientHello messages differently than other TLS implementations,
which might result in bypassing security restrictions
(CVE-2026-123640).
*) Security: worker processes might get caught in an endless loop while
reading the request body over SSL (CVE-2026-118899).
*) Change: now header lines without a colon are rejected.
*) Change: now a request is rejected if the chunked request body
contains too much framing overhead.
*) Bugfix: a buffer overflow might occur in a worker process when using
a GeoIP database in the MMDB format containing invalid coordinates.
*) Bugfix: a request might hang if it was proxied while the request body
was being discarded.
*) Bugfix: some values of the QPACK static table were decoded
incorrectly when using HTTP/3.
*) Bugfix: when using HTTP/2, response trailers might delay data of
higher priority streams.
*) Bugfix: the $cookie_... variables and the ngx_http_userid_module
handled the "Cookie" request header line incorrectly if it contained
a cookie without a name.
*) Bugfix: non-cacheable variables in the "index" directive might be
evaluated incorrectly.
*) Bugfix: OCSP responses for client certificates with uncommon serial
numbers might be cached incorrectly when using the "ssl_ocsp_cache"
directive.
*) Bugfix: the control API did not respond to requests with a too long
request line.
1.31.8
*) Change in internal API: now the JSON parser reports strings with
escape sequences as separate events, and the
ngx_json_unescape_string() function decodes a string into a separate
buffer.
*) Change: now the path specified in the "working_directory" directive
is relative to nginx prefix directory, but not to the current
directory.
*) Bugfix: worker processes exited on start or during reconfiguration if
an invalid directory was specified in the "working_directory"
directive.
*) Bugfix: worker processes might be terminated abnormally on a SIGBUS
signal when using HTTP/3 on platforms with strict alignment
requirements.
*) Bugfix: "recv() failed (5: Input/output error)" alerts might appear
in logs when closing SSL connections if kernel TLS was used with
OpenSSL 3.2.0 or newer.
*) Bugfix: nginx could not be built on Solaris if the --with-control-api
option was used.
1.31.7
*) Security: a buffer overflow might occur in a worker process when
using the "alias" directive if the request URI was changed by the
"rewrite" directive and was then mapped to a file path
(CVE-2026-15176).
*) Security: a buffer overflow might occur in a worker process while
evaluating string expressions with variables, which affected the
document root calculation and request logging in the http and stream
modules (CVE-2026-93479).
*) Security: when using HTTP/3 a part of an unknown frame might be
treated as the request body, which might result in bypassing the
"client_max_body_size" limit or injecting data in the proxied request
(CVE-2026-95101).
*) Security: when using TLS session ticket key rotation, one of the keys
was left uninitialized, which might allow to forge a session
(CVE-2026-97629).
*) Security: when using asynchronous file I/O (AIO), use-after-free
might occur in certain configurations if the SSI page has "include
virtual" commands (CVE-2026-97205).
*) Feature: the ngx_http_geoip_module and ngx_stream_geoip_module now
support databases in the MaxMind DB (MMDB) format.
*) Feature: now backend SSL certificates can be verified by IP address.
*) Feature: now QUIC supports reconfiguration and binary upgrade when
using the "quic_bpf" directive.
*) Change: the ngx_http_v2_module now uses the RFC 9218 prioritization
scheme, and RFC 7540 priority signals are ignored.
*) Bugfix: a segmentation fault might occur in a worker process or
"request count is zero" alerts might appear in logs if the
"X-Accel-Redirect" header line was cached and the cached response was
then served to a client.
*) Bugfix: a segmentation fault might occur in a worker process if the
ngx_http_dav_module was used to handle COPY and MOVE methods in a
location with the "alias" directive.
*) Bugfix: QUIC connections might be closed with the "quic flood
detected" message in logs if the "http3_stream_buffer_size" directive
was set to a small value; the bug had appeared in 1.27.5.
*) Bugfix: closing an SSL connection without close_notify was treated as
a clean shutdown, including the case when the connection was reset;
now "SSL_read() failed" errors appear in logs in this case.
*) Bugfix: "[crit] SSL_write() failed" messages might appear in logs
when an error occurred while reading from an SSL connection.
1.31.6
*) Security: a heap memory buffer overflow might occur in a worker
process under certain configurations when using HTTP/3 with OpenSSL
3.5.0 and earlier (CVE-2026-90439).
*) Change: now the QUIC transport parameters extension received in an
SSL connection is always ignored.
*) Bugfix: binary upgrade refused to work if the control API socket was
specified and the new nginx executable was built with the
ngx_http_perl_module.
*) Bugfix: an error while evaluating a predicate in a predicate location
was ignored and the predicate was treated as false.
*) Bugfix: an error during a nested location lookup might be ignored if
locations given by regular expressions or predicates were configured
at the current level.
*) Bugfix: a segmentation fault might occur while reading configuration
if the "geo" directive with the "ranges" parameter was used and the
corresponding binary base file was corrupted.
1.31.5
*) Feature: control API.
*) Feature: predicate locations.
*) Feature: the ngx_http_json_module.
*) Feature: the "client_body_early_read" directive.
*) Bugfix: use-after-free might occur in a worker process if proxying
with buffering was used and an error occurred while sending the
response to an HTTP/2 client.
*) Bugfix: a worker process might not exit or "accept4() failed (9: Bad
file descriptor)" alerts might appear in logs if the worker process
ran out of file descriptors before graceful shutdown.
*) Bugfix: requests to FastCGI and uwsgi backends were malformed if a
parameter name was too long.
*) Bugfixes in HTTP/3, ngx_http_slice_module, and
ngx_http_memcached_module.
1.31.4
*) Feature: the "proxy_protocol" directive in the stream and mail
modules now supports the PROXY protocol version 2.
*) Change: now HTTP/2 and gRPC requests to backends are always sent with
the ":authority" pseudo-header, and HTTP/1.1 requests - with the
"Host" header.
*) Bugfix: a segmentation fault might occur in a worker process if the
"select" method was used.
*) Bugfix: incomplete gRPC responses with a non-zero "Content-Length"
header line are now treated as malformed.
*) Bugfix: in binary compatibility with third-party modules using script
codes; the bug had appeared in 1.31.3.
*) Bugfix: in the ngx_http_perl_module.
*) Bugfixes in HTTP/2, HTTP/3, ngx_http_image_filter_module, and
ngx_http_grpc_module.
1.31.3
*) Security: heap buffer overflow might occur in a worker process when
using the map directive with regex matching if the map variable was
included in a string expression after a capture affected by this map;
a similar issue might happen when using a non-cacheable variable in a
string expression (CVE-2026-42533).
*) Security: uninitialized memory access might occur when using unnamed
regex captures with the "slice" directive or background cache update,
which could result in worker process memory disclosure or worker
process termination (CVE-2026-60005).
*) Security: use-after-free might occur when processing a specially
crafted proxied backend response with the ngx_http_ssi_filter_module
(CVE-2026-56434).
*) Change: the size of headers and trailers in HTTP/2 responses in the
ngx_http_proxy_v2_module and ngx_http_grpc_module is now limited with
"proxy_buffer_size" and "grpc_buffer_size" directives.
*) Change: loading of external entities is now disabled in the
ngx_http_xslt_filter_module.
*) Feature: the "xml_external_entities" directive in the
ngx_http_xslt_filter_module.
*) Feature: the "proxy_socket_sndbuf", "proxy_socket_rcvbuf",
"fastcgi_socket_sndbuf", "fastcgi_socket_rcvbuf",
"grpc_socket_sndbuf", "grpc_socket_rcvbuf", "scgi_socket_sndbuf",
"scgi_socket_rcvbuf", "uwsgi_socket_sndbuf", "uwsgi_socket_rcvbuf",
"tunnel_socket_sndbuf", and "tunnel_socket_rcvbuf" directives.
*) Feature: cache line size detection for loongarch64.
*) Bugfix: now nginx rejects HTTP/2 requests with out-of-order
pseudo-headers.
*) Bugfix: in flow control in the ngx_http_v2_module.
*) Bugfix: "[error] upstream sent frame for unknown stream" and "[crit]
cache file ... contains invalid header" messages might appear in logs
when sending a cached HTTP/2 response in the ngx_http_proxy_v2_module
if the "proxy_cache_revalidate" directive was used.
*) Bugfix: nginx might send the "Upgrade" header line in HTTP/2 and
HTTP/3 responses.
*) Bugfix: in the ngx_http_perl_module.
*) Bugfix: IPv6 fragmentation might not be disabled when using QUIC on
some operating systems.
*) Bugfix: in the ngx_http_auth_basic_module on Solaris.
*) Bugfixes and improvements in the ngx_http_tunnel_module.
1.31.2
*) Security: use-after-free might occur when using HTTP/3 and processing
a specially crafted QUIC session, allowing an attacker to cause
worker process memory corruption or segmentation fault in a worker
process (CVE-2026-42530).
*) Security: a heap memory buffer overflow might occur in a worker
process when using a configuration with "ignore_invalid_headers off;"
and "large_client_header_buffers" with large configured values when
proxying a specially crafted request to HTTP/2 or gRPC backend,
allowing an attacker to cause worker process memory corruption or
segmentation fault in a worker process (CVE-2026-42055).
*) Security: a heap memory buffer overread might occur in a worker
process while handling a specially sent response with decoding from
UTF-8 via the "charset_map" directive, allowing an attacker to cause
a limited disclosure of worker proccess memory or segmentation fault
in a worker process (CVE-2026-48142).
*) Change: now the $request_id variable uses SipHash-2-4.
*) Feature: the $ssl_sigalgs variable.
*) Bugfix: a variable defined by the "split_clients" directive might be
empty if all percentages were specified explicitly and summed up to
100%.
*) Bugfix: constant time "secure_link" hash comparison.
1.31.1
*) Security: a heap memory buffer overflow might occur in a worker
process when using a configuration with overlapping captures in
ngx_http_rewrite_module, potentially resulting in arbitrary code
execution (CVE-2026-9256).
1.31.0
*) Security: when using the "proxy_set_body" directive, an attacker
might inject data in the proxied request to an HTTP/2 backend
(CVE-2026-42926).
*) Security: a heap memory buffer overflow might occur in a worker
process while handling a specially crafted request by
ngx_http_rewrite_module, potentially resulting in arbitrary code
execution (CVE-2026-42945).
*) Security: a heap memory buffer overread might occur in a worker
process while handling a specially crafted response by
ngx_http_scgi_module or ngx_http_uwsgi_module, allowing an attacker
to cause a disclosure of worker process memory or segmentation fault
in a worker process (CVE-2026-42946).
*) Security: a heap memory buffer overread might occur in a worker
process while handling a specially sent response with decoding from
UTF-8 via the "charset_map" directive, allowing an attacker to cause
a limited disclosure of worker proccess memory or segmentation fault
in a worker process (CVE-2026-42934).
*) Security: when using HTTP/3, processing of connection migration might
cause new QUIC streams to receive a new client address before
validation, allowing an attacker to cause address spoofing
(CVE-2026-40460).
*) Security: use-after-free might occur during DNS server response
processing if the "ssl_ocsp" directive was used, allowing an attacker
to cause worker process memory corruption or segmentation fault in a
worker process (CVE-2026-40701).
*) Change: now nginx rejects HTTP/2 and HTTP/3 requests with the
"Connection", "Proxy-Connection", "Keep-Alive", "Transfer-Encoding",
"Upgrade" header lines, and "TE" with any value other than
"trailers".
*) Change: the ngx_http_dav_module now rejects a COPY or MOVE requests
when the source and destination resources are the same or have a
parent-child collection relationship.
*) Change: the logging level of the "invalid alert" and "record layer
failure" SSL errors, and of the "SSL alert number N" for any alert
numbers has been lowered from "crit" to "info".
*) Change: now the "sticky" module can be disabled with the
--without-http_upstream_sticky_module configure option; the
--without-http_upstream_sticky configure option is deprecated.
*) Feature: the ngx_http_tunnel_module; support for authenticating to
proxies in the "auth_basic", "satisfy", and "auth_delay" directives.
*) Feature: the "least_time" directive inside the "upstream" block.
*) Feature: the "proxy_ssl_alpn" directive in the stream module.
*) Bugfix: connections with HTTP/2 backends might not be cached when
using the "proxy_set_body" or "proxy_pass_request_body" directives.
*) Bugfix: proxied HTTP/0.9, SCGI, or uWSGI responses might be
transferred incorrectly if the first line was not fully read.
1.29.8
*) Feature: the "max_headers" directive.
*) Feature: OpenSSL 4.0 compatibility.
*) Feature: now the "include" directive inside the "geo" block supports
wildcards.
*) Bugfix: in processing of HTTP 103 (Early Hints) responses from a
proxied backend.
*) Bugfix: the $request_port and $is_request_port variables were not
available in subrequests.
1.29.7
*) Security: a buffer overflow might occur while handling a COPY or MOVE
request in a location with "alias", allowing an attacker to modify
the source or destination path outside of the document root
(CVE-2026-27654).
*) Security: processing of a specially crafted mp4 file by the
ngx_http_mp4_module on 32-bit platforms might cause a worker process
crash, or might have potential other impact (CVE-2026-27784).
*) Security: processing of a specially crafted mp4 file by the
ngx_http_mp4_module might cause a worker process crash, or might have
potential other impact (CVE-2026-32647).
*) Security: a segmentation fault might occur in a worker process if the
CRAM-MD5 or APOP authentication methods were used and authentication
retry was enabled (CVE-2026-27651).
*) Security: an attacker might use PTR DNS records to inject data in
auth_http requests, as well as in the XCLIENT command in the backend
SMTP connection (CVE-2026-28753).
*) Security: SSL handshake might succeed despite OCSP rejecting a client
certificate in the stream module (CVE-2026-28755).
*) Feature: the "multipath" parameter of the "listen" directive.
*) Feature: the "local" parameter of the "keepalive" directive in the
"upstream" block.
*) Change: now the "keepalive" directive in the "upstream" block is
enabled by default.
*) Change: now ngx_http_proxy_module supports keepalive by default; the
default value for "proxy_http_version" is "1.1"; the "Connection"
proxy header is not sent by default anymore.
*) Bugfix: an invalid HTTP/2 request might be sent after switching to
the next upstream if buffered body was used in the
ngx_http_grpc_module.
1.29.6
*) Feature: session affinity support; the "sticky" directive in the
"upstream" block of the "http" module; the "server" directive
supports the "route" and "drain" parameters.
*) Change: now nginx limits the size and rate of QUIC stateless reset
packets.
*) Bugfix: receiving a QUIC packet by a wrong worker process could cause
the connection to terminate.
*) Bugfix: "[crit] cache file ... contains invalid header" messages
might appear in logs when sending a cached HTTP/2 response.
*) Bugfix: proxying to scgi backends might not work when using chunked
transfer encoding and the "scgi_request_buffering" directive.
*) Bugfix: in the ngx_http_mp4_module.
*) Bugfix: nginx treated a comma as separator in the "Cookie" request
header line when evaluating "$cookie_..." variables.
*) Bugfix: in IMAP command literal argument parsing.
1.29.5
*) Security: an attacker might inject plain text data in the response
from an SSL backend (CVE-2026-1642).
*) Bugfix: use-after-free might occur after switching to the next gRPC
or HTTP/2 backend.
*) Bugfix: an invalid HTTP/2 request might be sent after switching to
the next upstream.
*) Bugfix: a response with multiple ranges might be larger than the
source response.
*) Bugfix: fixed setting HTTP_HOST when proxying to FastCGI, SCGI, and
uwsgi backends.
*) Bugfix: fixed warning when compiling with MSVC 2022 x86.
*) Change: the logging level of the "ech_required" SSL error has been
lowered from "crit" to "info".
1.29.4
*) Feature: the ngx_http_proxy_module supports HTTP/2.
*) Feature: Encrypted ClientHello TLS extension support when using
OpenSSL ECH feature branch; the "ssl_ech_file" directive.
*) Change: validation of host and port in the request line, "Host"
header field, and ":authority" pseudo-header field has been changed
to follow RFC 3986.
*) Change: now a single LF used as a line terminator in a chunked
request or response body is considered an error.
*) Bugfix: when using HTTP/3 with OpenSSL 3.5.1 or newer a segmentation
fault might occur in a worker process; the bug had appeared in
1.29.1.
*) Bugfix: a segmentation fault might occur in a worker process if the
"try_files" directive and "proxy_pass" with a URI were used.
1.29.3
*) Feature: the "add_header_inherit" and "add_trailer_inherit"
directives.
*) Feature: the $request_port and $is_request_port variables.
*) Feature: the $ssl_sigalg and $ssl_client_sigalg variables.
*) Feature: the "volatile" parameter of the "geo" directive.
*) Feature: now certificate compression is available with BoringSSL.
*) Bugfix: now certificate compression is disabled with OCSP stapling.
1.29.2
*) Feature: now nginx can be built with AWS-LC.
*) Bugfix: now the "ssl_protocols" directive works in a virtual server
different from the default server when using OpenSSL 1.1.1 or newer.
*) Bugfix: SSL handshake always failed when using TLSv1.3 with OpenSSL
and client certificates and resuming a session with a different SNI
value; the bug had appeared in 1.27.4.
*) Bugfix: the "ignoring stale global SSL error" alerts might appear in
logs when using QUIC and the "ssl_reject_handshake" directive; the
bug had appeared in 1.29.0.
*) Bugfix: in delta-seconds processing in the "Cache-Control" backend
response header line.
*) Bugfix: an XCLIENT command didn't use the xtext encoding.
*) Bugfix: in SSL certificate caching during reconfiguration.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
lfs/nginx | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/lfs/nginx b/lfs/nginx
index 59b670c61..f3b87cdc6 100644
--- a/lfs/nginx
+++ b/lfs/nginx
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2025 IPFire Team <info@ipfire.org> #
+# Copyright (C) 2007-2026 IPFire Team <info@ipfire.org> #
# #
# This program is free software: you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
@@ -25,7 +25,7 @@
include Config
SUMMARY = A HTTP server and IMAP/POP3 proxy server
-VER = 1.29.1
+VER = 1.31.9
THISAPP = nginx-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -33,7 +33,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = nginx
-PAK_VER = 18
+PAK_VER = 19
DEPS =
@@ -47,7 +47,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = ab2f49ff5564fa45f86732e92abf8a43ce5f225cfcffcd66f40c7e35377525fe18a7760c1946e6e9f48e7fc07e99fdefa4ea5c19deae3cde00121aefa3d7cc14
+$(DL_FILE)_BLAKE2 = fc88e5899575b6f82a8427fc0db21a0c9868a52b605cf146b482cb56b997f13f03dfbec23296929679100ec506826cc6e7643119f7737f6b1acc3eada311f4d5
install : $(TARGET)
--
2.56.1
next prev parent reply other threads:[~2026-11-19 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 13:55 [PATCH] clamav: Update to version 1.5.5 Adolf Belka
2026-11-19 13:55 ` [PATCH] core207: Ship gnutls Adolf Belka
2026-11-19 13:55 ` [PATCH] gnutls: Update to version 3.8.14 Adolf Belka
2026-11-19 13:55 ` [PATCH] haproxy: Update to version 3.4.8 Adolf Belka
2026-11-19 13:55 ` Adolf Belka [this message]
2026-11-19 13:55 ` [PATCH] ruby: Update to version 4.0.10 Adolf Belka
2026-11-19 13:55 ` [PATCH] tshark: Update to version 4.6.10 Adolf Belka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261119135512.3276857-5-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox