Node.js shipped the October 21 security releases. The project rates the top issues high.
Node.js published October 21 security releases: 26.12.1, 24.22.1, and 22.23.4. The project rates the top issues high. End-of-life lines are not patched.
The short version
The Node.js project says the October 21, 2026 security releases are 26.12.1, 24.22.1, and 22.23.4. It rates the highest issues high. It says end-of-life lines do not receive the fix. A certificate-store update in the same notes is tied to the eMudhra intermediates, which is a separate document.
The release page is the record
On October 21, 2026 the Node.js project published security releases for the 26.x, 24.x, and 22.x lines. The versions it names are 26.12.1, 24.22.1, and 22.23.4. The project says the highest severity in each of those lines is high. The GitHub tag for 22.23.4 is the matching source drop for that line. Vercel's bulletin is another account of the same release, plus Vercel's own statement about runtimes it operates. This page follows the project on version numbers. Asked directly, Is the eMudhra certificate note a second bug writeup? No. The release list includes a certificate-store update the project labels as the eMudhra intermediate matter. The exit and the block are separate briefs.what a CVE identifier is.
The high issues stay named, not demonstrated
The project lists CVE-2026-111497 as a flaw in its Brotli decoder and says that flaw can permit remote code execution. It also rates TLS hostname checks and a DNS resolver check as high. Those sentences are enough to say why the release exists. They are not a recipe, a sample input, or a decoder trace. A reader who maintains Node needs the version. A reader who wants the triggering bytes wants the advisory, and will not find them rewritten here. An October 24 brief follows the same identifier into Bun and the upstream library lines, which are a different product surface from these installers.the same identifier beyond Node.
End of life is outside the fix
The project says end-of-life lines are affected when a security release ships and do not receive the fix. Vercel says the same about Node.js 20 on its platform: that line is at end of life and will not get this patch, so a project still on it has to move to a supported line. A hosted runtime that Vercel updates is not a patch for a process someone else runs. The version pin still has to change where the process actually starts.what the KEV catalog adds.
One line in the notes is the certificate store
The project's dependency list includes a certificate update it labels as the eMudhra intermediate compromise, alongside other library bumps. That label points at a certificate story this paper already filed: the browser blocks, and the company's later decision to leave the global TLS business. A runtime that updates its trust store is not the company that issued the certificates, and it is not a finding that every Node process was presenting an eMudhra certificate. It is a store update in a security release.eMudhra's blocked intermediates.
Vercel is a platform account
Vercel says it deployed rules on its edge the same day and is rolling the patched Node versions across runtimes it manages. It also says a project that runs Node outside those runtimes still has to upgrade. A platform bulletin is evidence about that platform. It is not a census of who installed 22.23.4. This page will not adopt Vercel's description of an attack path as a procedure. The useful sentence is the split: managed runtimes and everywhere else. CISA later put the same Brotli identifier on KEV.Brotli on CISA KEV.
What this page will not print
It will not print inputs, decoder states, or a list of files to delete. The advisory's job is the fix and the severity. A news brief can name the versions, the lines, the high rating, and the separate certificate-store note. People who need a proof of concept are not the audience. People who need to know which installer to fetch are. Asked directly, Does this page explain how the Brotli issue is triggered? No. The project names CVE-2026-111497 and rates it high. The mechanism stays in the advisory. This page names the release.a signature on a package.
Who is in scope
Operators of Node.js 22, 24, or 26, including CI images and containers they build themselves. Operators of end-of-life lines, who are in scope as people the project says will not get the fix. People who do not run Node are outside it. A service that only proxies to a Node process is in scope only for the process, not for the proxy. Asked directly, What does Vercel add? Vercel says it rolled its own rules and is updating runtimes it manages. That account does not patch a Node process Vercel does not run.the advisory is the story.
What stays on the record
October 21, 2026. Versions 26.12.1, 24.22.1, and 22.23.4. Highest severity high, on the project's rating. CVE-2026-111497 named as a Brotli decoder issue the project says can permit code execution. TLS hostname checks and a DNS check also rated high. Certificate-store update labeled as the eMudhra intermediate matter. End-of-life lines unpatched. Vercel describes its own rollout and says other hosts still upgrade. Asked directly, Which lines does the project say are updated? 26.x, 24.x, and 22.x, as 26.12.1, 24.22.1, and 22.23.4. The project says end-of-life lines are affected and do not get this fix.what an advisory must name.
What would move the row
A Node.js correction of a version number, or a later release that supersedes these three, would replace the row. Evidence about exploitation in the wild would be a different document and is not in the project post this page is using. Until then the record is the security release, the 22.23.4 tag, and Vercel's account of its own platform. The short answer this page will stand on is this: The Node.js project says the October 21, 2026 security releases are 26.12.1, 24.22.1, and 22.23.4. It rates the highest issues high. It says end-of-life lines do not receive the fix. A certificate-store update in the same notes is tied to the eMudhra intermediates, which is a separate document.eMudhra leaves the TLS business.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
Does this page explain how the Brotli issue is triggered?
No. The project names CVE-2026-111497 and rates it high. The mechanism stays in the advisory. This page names the release.
Which lines does the project say are updated?
26.x, 24.x, and 22.x, as 26.12.1, 24.22.1, and 22.23.4. The project says end-of-life lines are affected and do not get this fix.
What does Vercel add?
Vercel says it rolled its own rules and is updating runtimes it manages. That account does not patch a Node process Vercel does not run.
Is the eMudhra certificate note a second bug writeup?
No. The release list includes a certificate-store update the project labels as the eMudhra intermediate matter. The exit and the block are separate briefs.
Are the TLS and DNS issues given as recipes here?
No. The project rates hostname checks and a DNS name check as high. This page does not describe the inputs.