From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: buildroot@buildroot.org, Bernd Kuhls <bernd@kuhls.net>
Subject: Re: [Buildroot] [PATCH 1/1] package/nghttp2: security bump version to 1.70.0
Date: Fri, 23 Oct 2026 09:31:54 +0200 [thread overview]
Message-ID: <atsNY7X6T5l8o0Hy@windsurf> (raw)
In-Reply-To: <20261022235328.3259902-1-fiona.klute@gmx.de>
On Fri, Oct 23, 2026 at 01:53:28AM +0200, Fiona Klute via buildroot wrote:
> CVE-2026-58055 [1]: nghttp2's nghttpx proxy through 1.69.0 forwards an
> HTTP/1.1 Upgrade request that also carries a Content-Length header and
> body onto reusable keep-alive backend connections, re-adding the
> Upgrade and Connection headers while passing Content-Length
> verbatim. A backend that resolves the resulting ambiguous message in
> the attacker's favor enables HTTP request/response smuggling and
> cross-client response-queue poisoning.
>
> Upstream changelogs (no specific mentions of security):
> https://github.com/nghttp2/nghttp2/releases/tag/v1.70.0
> https://github.com/nghttp2/nghttp2/releases/tag/v1.69.0
>
> [1] https://nvd.nist.gov/vuln/detail/cve-2026-58055
>
> Signed-off-by: Fiona Klute <fiona.klute@gmx.de>
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-23 7:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 23:53 [Buildroot] [PATCH 1/1] package/nghttp2: security bump version to 1.70.0 Fiona Klute via buildroot
2026-10-23 7:31 ` 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=atsNY7X6T5l8o0Hy@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=fiona.klute@gmx.de \
--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