From: Jason Schonberg <schonm@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Jason Schonberg <schonm@gmail.com>
Subject: [meta-oe][wrynose][PATCH] nodejs: 22.23.3 -> 22.23.4
Date: Sat, 31 Oct 2026 00:15:13 -0400 [thread overview]
Message-ID: <20261031041513.261844-1-schonm@gmail.com> (raw)
This is the October 2026 security release.
4 high severity issues.
3 medium severity issues.
3 low severity issue.
High severity issues.
CVE-2026-105482
CVE-2026-105483
CVE-2026-106069
CVE-2026-111497
Medium severity issues.
CVE-2026-105481
CVE-2026-106072
CVE-2026-106074
Low severity issues.
CVE-2026-106070 (affects only nodejs v26)
CVE-2026-106071 (affects only nodejs v26)
CVE-2026-106073
https://nodejs.org/en/blog/vulnerability/october-2026-security-releases
Changelog: https://github.com/nodejs/node/releases/tag/v22.23.4
Signed-off-by: Jason Schonberg <schonm@gmail.com>
---
.../nodejs/{nodejs_22.23.3.bb => nodejs_22.23.4.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-oe/recipes-devtools/nodejs/{nodejs_22.23.3.bb => nodejs_22.23.4.bb} (99%)
diff --git a/meta-oe/recipes-devtools/nodejs/nodejs_22.23.3.bb b/meta-oe/recipes-devtools/nodejs/nodejs_22.23.4.bb
similarity index 99%
rename from meta-oe/recipes-devtools/nodejs/nodejs_22.23.3.bb
rename to meta-oe/recipes-devtools/nodejs/nodejs_22.23.4.bb
index 1a8a50434c..4dedfe36f8 100644
--- a/meta-oe/recipes-devtools/nodejs/nodejs_22.23.3.bb
+++ b/meta-oe/recipes-devtools/nodejs/nodejs_22.23.4.bb
@@ -39,7 +39,7 @@ SRC_URI:append:class-target = " \
SRC_URI:append:toolchain-clang:powerpc64le = " \
file://0001-ppc64-Do-not-use-mminimal-toc-with-clang.patch \
"
-SRC_URI[sha256sum] = "bd97093e1a1e9243338950c174a693a64d4e0926a9c6ce259962bc58d5e96909"
+SRC_URI[sha256sum] = "7b9adc82d612d0a2a863d96c46de2292552e250cee51956ebbe0146c42aacae9"
S = "${UNPACKDIR}/node-v${PV}"
--
2.43.0
reply other threads:[~2026-10-31 4:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261031041513.261844-1-schonm@gmail.com \
--to=schonm@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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