From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Christian Stewart <christian@aperture.us>
Cc: buildroot@buildroot.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
James Hilliard <james.hilliard1@gmail.com>,
Thomas Perale <thomas.perale@mind.be>
Subject: Re: [Buildroot] [PATCH v1 1/1] package/go: bump to version 1.26.2
Date: Fri, 10 Apr 2026 14:04:30 +0200 [thread overview]
Message-ID: <bb84af0a2992f6515979f5dd0a8fe31a@free.fr> (raw)
In-Reply-To: <20260410043308.42434-1-christian@aperture.us>
On 10/04/2026 06:33, Christian Stewart via buildroot wrote:
> go1.26.2 (released 2026-04-07) includes security fixes to the go
> command, the
> compiler, and the archive/tar, crypto/tls, crypto/x509, html/template,
> and os
> packages, as well as bug fixes to the go command, the go fix command,
> the
> compiler, the linker, the runtime, and the net, net/http, and net/url
> packages.
>
> CVE-2026-32289: html/template: JS template literal context incorrectly
> tracked
> CVE-2026-33810: crypto/x509: excluded DNS constraints not properly
> applied to wildcard domains
> CVE-2026-27144: cmd/compile: no-op interface conversion bypasses
> overlap checking
> CVE-2026-27143: cmd/compile: possible memory corruption after bound
> check elimination
> CVE-2026-32288: archive/tar: unbounded allocation when parsing old
> format GNU sparse map
> CVE-2026-32283: crypto/tls: multiple key update handshake messages can
> cause connection to deadlock
> CVE-2026-27140: cmd/go: trust layer bypass when using cgo and SWIG
> CVE-2026-32280: crypto/x509: unexpected work during chain building
> CVE-2026-32281: crypto/x509: inefficient policy validation
>
> https://go.dev/doc/devel/release#go1.26.2
> https://github.com/golang/go/issues?q=milestone%3AGo1.26.2+label%3ACherryPickApproved
>
> Signed-off-by: Christian Stewart <christian@aperture.us>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-04-10 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 4:33 [Buildroot] [PATCH v1 1/1] package/go: bump to version 1.26.2 Christian Stewart via buildroot
2026-04-10 12:04 ` 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=bb84af0a2992f6515979f5dd0a8fe31a@free.fr \
--to=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=james.hilliard1@gmail.com \
--cc=ju.o@free.fr \
--cc=thomas.perale@mind.be \
--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