buildroot.buildroot.org archive mirror
 help / color / mirror / Atom feed
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: security bump to version 1.26.5
Date: Tue, 14 Jul 2026 10:26:33 +0200	[thread overview]
Message-ID: <6b24eae38d18d91ce74fb7c4935fe1ee@free.fr> (raw)
In-Reply-To: <20260713203901.24229-1-christian@aperture.us>

On 13/07/2026 22:39, Christian Stewart via buildroot wrote:
> Fixes the following security issues:
> 
> CVE-2026-39822: os: root escape via symlink plus trailing slash
> 
> go1.26.5 (released 2026-07-07) includes security fixes to the 
> crypto/tls and os packages, as well as bug fixes to the compiler, the 
> runtime, the go command, and the net, os, and syscall packages.
> 
> https://go.dev/doc/devel/release#go1.26.5
> 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

  reply	other threads:[~2026-07-14  8:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13 20:39 [Buildroot] [PATCH v1 1/1] package/go: security bump to version 1.26.5 Christian Stewart via buildroot
2026-07-14  8:26 ` Julien Olivain via buildroot [this message]
2026-07-17 15:47 ` Thomas Perale via buildroot
2026-07-31 12:04 ` Thomas Perale via buildroot

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=6b24eae38d18d91ce74fb7c4935fe1ee@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;
as well as URLs for NNTP newsgroup(s).