From: Jason Schonberg <schonm@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Jason Schonberg <schonm@gmail.com>
Subject: [meta-oe][PATCH] nodejs: upgrade 24.22.2 -> 24.22.3
Date: Wed, 11 Nov 2026 19:45:48 -0500 [thread overview]
Message-ID: <20261112004548.4996-1-schonm@gmail.com> (raw)
This is the November 2026 security release.
7 high severity issues.
6 medium severity issues.
3 low severity issues.
High severity issues.
CVE-2026-123863
CVE-2026-123864
CVE-2026-123865
CVE-2026-123866
CVE-2026-126051
CVE-2026-123872
CVE-2026-123874
Medium severity issues.
CVE-2026-123828
CVE-2026-123867
CVE-2026-123868
CVE-2026-123871
CVE-2026-123877
CVE-2026-123875
Low severity issues.
CVE-2026-123829
CVE-2026-123862
CVE-2026-106071
https://nodejs.org/en/blog/vulnerability/november-2026-security-releases
Changelog: https://github.com/nodejs/node/releases/tag/v24.22.3
Signed-off-by: Jason Schonberg <schonm@gmail.com>
---
.../nodejs/{nodejs_24.22.2.bb => nodejs_24.22.3.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-oe/recipes-devtools/nodejs/{nodejs_24.22.2.bb => nodejs_24.22.3.bb} (98%)
diff --git a/meta-oe/recipes-devtools/nodejs/nodejs_24.22.2.bb b/meta-oe/recipes-devtools/nodejs/nodejs_24.22.3.bb
similarity index 98%
rename from meta-oe/recipes-devtools/nodejs/nodejs_24.22.2.bb
rename to meta-oe/recipes-devtools/nodejs/nodejs_24.22.3.bb
index fc4eb60ebd..f9b4eea38e 100644
--- a/meta-oe/recipes-devtools/nodejs/nodejs_24.22.2.bb
+++ b/meta-oe/recipes-devtools/nodejs/nodejs_24.22.3.bb
@@ -36,7 +36,7 @@ SRC_URI = "https://nodejs.org/dist/v${PV}/node-v${PV}.tar.xz \
SRC_URI:append:class-target = " \
file://0009-Using-native-binaries.patch \
"
-SRC_URI[sha256sum] = "8fe2ec1723bb9f8d0b683907c82708debbeda64af21cb2aa214c4241eed0a061"
+SRC_URI[sha256sum] = "48ca3aa8a9b02133356922ef4fc80200e00598c80a4ef446f7c39a459222593d"
S = "${UNPACKDIR}/node-v${PV}"
--
2.43.0
reply other threads:[~2026-11-12 0:45 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=20261112004548.4996-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 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.