Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/nginx: security bump to v1.30.7
Date: Wed, 18 Nov 2026 22:12:33 +0100	[thread overview]
Message-ID: <7d13596db2c11636e4bd3f374d4605c2@free.fr> (raw)
In-Reply-To: <20261118204420.332438-1-thomas.perale@mind.be>

On 18/11/2026 21:44, Thomas Perale via buildroot wrote:
> For more information about the release, see:
>  - https://nginx.org/en/CHANGES-1.30
>  - https://lwn.net/Articles/1108362/
> 
> This fixes the following vulnerabilities:
> 
> - CVE-2026-125283: a buffer overflow might occur in a worker process
>   when using the "try_files" and "alias" directives in certain
>   configurations.
>   https://www.cve.org/CVERecord?id=CVE-2026-125283
> 
> - CVE-2026-123007: 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.
>   https://www.cve.org/CVERecord?id=CVE-2026-123007
> 
> - CVE-2026-123633: use-after-free might occur in a worker process when
>   using HTTP/2 if worker_connections were not enough.
>   https://www.cve.org/CVERecord?id=CVE-2026-123633
> 
> - CVE-2026-121810: use-after-free might occur in a worker process when
>   using HTTP/3 if worker_connections were not enough.
>   https://www.cve.org/CVERecord?id=CVE-2026-121810
> 
> - CVE-2026-123634: 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.
>   https://www.cve.org/CVERecord?id=CVE-2026-123634
> 
> - CVE-2026-113425: use-after-free might occur in a worker process in 
> the
>   mail proxy server.
>   https://www.cve.org/CVERecord?id=CVE-2026-113425
> 
> - CVE-2026-120967: 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.
>   https://www.cve.org/CVERecord?id=CVE-2026-120967
> 
> - CVE-2026-123640: the ngx_stream_ssl_preread_module might interpret
>   malformed ClientHello messages differently than other TLS
>   implementations, which might result in bypassing security 
> restrictions
>   https://www.cve.org/CVERecord?id=CVE-2026-123640
> 
> - CVE-2026-118899: worker processes might get caught in an endless loop
>   while reading the request body over SSL.
>   https://www.cve.org/CVERecord?id=CVE-2026-118899
> 
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>

Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-11-18 21:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-18 20:44 [Buildroot] [PATCH 1/1] package/nginx: security bump to v1.30.7 Thomas Perale via buildroot
2026-11-18 21:12 ` Julien Olivain 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=7d13596db2c11636e4bd3f374d4605c2@free.fr \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=thomas.perale@mind.be \
    /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