From: "Stefan Müller via buildroot" <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: "Stefan Müller" <stefan.mueller@rey-technology.com>
Subject: [Buildroot] [PATCH 3/5] package/libssh2: fix CVE-2026-66033
Date: Thu, 20 Aug 2026 06:56:44 +0000 [thread overview]
Message-ID: <20260820065646.375321-4-stefan.mueller@rey-technology.com> (raw)
In-Reply-To: <20260820065646.375321-1-stefan.mueller@rey-technology.com>
[-- Attachment #1.1: Type: text/html, Size: 10159 bytes --]
[-- Attachment #1.2: linkedinmedium_e5ee0685-3767-4ffd-a5c5-9e4e3fc32352.png --]
[-- Type: image/png, Size: 1525 bytes --]
[-- Attachment #1.3: instagrammedium_908c8ebd-b03d-4881-a6e2-043808ead83d.png --]
[-- Type: image/png, Size: 1912 bytes --]
[-- Attachment #1.4: teamsmedium_9934c99a-98a5-42b7-9a66-2bebfdd7ebf1.png --]
[-- Type: image/png, Size: 1900 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-08-20 6:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4e118c97-1508-4315-bc90-2b0b02fc43b2.a680deba-e8f9-456f-ab7c-ac325426e0a3.7f9be450-dceb-4ebb-b9e9-685b8eeceb2d@emailsignatures365.codetwo.com>
2026-08-20 6:56 ` [Buildroot] [PATCH 0/5] package/libssh2: fix five security vulnerabilities Stefan Müller via buildroot
2026-08-20 6:56 ` [Buildroot] [PATCH 1/5] package/libssh2: fix CVE-2025-15661 Stefan Müller via buildroot
2026-08-20 6:56 ` [Buildroot] [PATCH 2/5] package/libssh2: fix CVE-2026-66032 Stefan Müller via buildroot
2026-08-20 6:56 ` Stefan Müller via buildroot [this message]
2026-08-20 6:56 ` [Buildroot] [PATCH 4/5] package/libssh2: fix CVE-2026-66034 Stefan Müller via buildroot
2026-08-20 6:56 ` [Buildroot] [PATCH 5/5] package/libssh2: fix CVE-2026-66035 Stefan Müller 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=20260820065646.375321-4-stefan.mueller@rey-technology.com \
--to=buildroot@buildroot.org \
--cc=stefan.mueller@rey-technology.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.