From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/nginx: security bump to version 1.30.6
Date: Thu, 22 Oct 2026 10:39:22 +0200 [thread overview]
Message-ID: <atnLtZAccKp0Bt0f@windsurf> (raw)
In-Reply-To: <20261022070004.2533972-1-peter@korsgaard.com>
On Thu, Oct 22, 2026 at 09:00:02AM +0200, Peter Korsgaard wrote:
> Fixes the following vulnerabilities:
>
> Changes with nginx 1.30.6 14 Oct 2026
>
> *) 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).
> Thanks to Matt Suiche of Tolmo Inc.
>
> *) 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).
> Thanks to Hansol Lee of GOTROOT.
>
> *) 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).
> Thanks to PhiNode Labs.
>
> *) 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).
> Thanks to cyberlancer.
>
> Changes with nginx 1.30.5 15 Sep 2026
>
> *) 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).
> Thanks to Banny Liao.
>
> Changes with nginx 1.30.4 15 Jul 2026
>
> *) 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).
> Thanks to Mufeed VH of Winfunc Research and Maxim Dounin.
>
> *) 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).
> Thanks to P4P3R-HAK.
>
> https://nginx.org/en/CHANGES-1.30
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Applied to master, thanks!
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-22 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 7:00 [Buildroot] [PATCH] package/nginx: security bump to version 1.30.6 Peter Korsgaard
2026-10-22 8:39 ` Thomas Petazzoni via buildroot [this message]
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=atnLtZAccKp0Bt0f@windsurf \
--to=buildroot@buildroot.org \
--cc=peter@korsgaard.com \
--cc=thomas.petazzoni@bootlin.com \
/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