# Node.js security update: fixed versions 22.23.4, 24.22.1 and 26.12.1 - Kind: Detail - URL: /articles/nodejs-security-update-october-2026 - Canonical: https://www.aeptus.com/articles/nodejs-security-update-october-2026/ - HTML lang: en-GB - H1: Node.js security update: fixed versions 22.23.4, 24.22.1 and 26.12.1 - Description: Node.js fixed four high severity flaws, including a Brotli issue that could permit remote code execution. Check every live runtime and deploy its matching patch. - Structured data: BlogPosting, BreadcrumbList, ImageObject, ListItem, WebPage - Internal links: 88 - Image coverage: 6/14 images with alt text - Summary: Node.js security update: fixed versions 22.23.4, 24.22.1 and 26.12.1. Node.js fixed four high severity flaws, including a Brotli issue that could permit remote code execution. Check every live runtime and deploy its matching patch.. Node.js security update: fixed versions 22.23.4, 24.22.1 and 26.12.1 - Related links: product-connect-and-prepare-data, product-collect-and-keep-evidence-current, product-report-with-confidence, work-with-ai-agents, automation - Outline: Section: Latest articles Canadian report maps security work in small businesses A review of public data looks at security staffin | Section: Editors’ picks Unauthorized radio signals stopped trains in Poland in 2023 In August 2023, unauthorized radio transmissi | Section: Explore Make security decisions 1 Prepare, respond and recover 2 Protect everyday business 2 Prove security and earn tru ## Section Latest articles Canadian report maps security work in small businesses A review of public data looks at security staffing, written policies and updates among Canadian businesses with 10 to 49 employees. INTERCEPT hosts free cybersecurity webinar for small teams The 18 November online event will cover phishing, multi-factor authentication and a cybersecurity learning platform. A third-party software vulnerability led to a data breach at Frontline Education Frontline has begun notifying people affected by an August incident involving two school administration products. The impact varies between districts and individuals. ## Section Editors’ picks Unauthorized radio signals stopped trains in Poland in 2023 In August 2023, unauthorized radio transmissions triggered Poland’s railway stop function. Reporting said the receiver did not verify who sent the command; no one was injured. A cyberattack disrupted refrigeration at hundreds of French supermarkets An attack on 12 October 2026 changed refrigeration settings and led stores to discard fresh and frozen food. CERT-FR named several affected controller families, warned that activity might continue and did not identify how access began. A secret is not rotated until the old credential stops working Railway’s preliminary report says some environment variables in at most 1.85% of workspaces may have been compromised, but it could not identify which specific variables were affected. Prove a rotation is complete by checking each consumer and confirming the old credential is revoked. ## Section Explore Make security decisions 1 Prepare, respond and recover 2 Protect everyday business 2 Prove security and earn trust 1 Understand threats and change 9 ## Section Topics ## LearnEditorialMobileSection Latest articles Canadian report maps security work in small businesses A review of public data looks at security staffing, written policies and updates among Canadian businesses with 10 to 49 employees. INTERCEPT hosts free cybersecurity webinar for small teams The 18 November online event will cover phishing, multi-factor authentication and a cybersecurity learning platform. A third-party software vulnerability led to a data breach at Frontline Education Frontline has begun notifying people affected by an August incident involving two school administration products. The impact varies between districts and individuals. View all articles → ## LearnEditorialMobileSection How-to Guides Answer security questionnaires without chaos A step-by-step way to respond faster without improvising every answer from scratch. View all guides → ## LearnEditorialMobileSection Editors’ picks Unauthorized radio signals stopped trains in Poland in 2023 In August 2023, unauthorized radio transmissions triggered Poland’s railway stop function. Reporting said the receiver did not verify who sent the command; no one was injured. A cyberattack disrupted refrigeration at hundreds of French supermarkets An attack on 12 October 2026 changed refrigeration settings and led stores to discard fresh and frozen food. CERT-FR named several affected controller families, warned that activity might continue and did not identify how access began. A secret is not rotated until the old credential stops working Railway’s preliminary report says some environment variables in at most 1.85% of workspaces may have been compromised, but it could not identify which specific variables were affected. Prove a rotation is complete by checking each consumer and confirming the old credential is revoked. ## LearnEditorialMobileSection Explore Article categories Make security decisions 1 Prepare, respond and recover 2 Protect everyday business 2 Prove security and earn trust 1 Understand threats and change 9 Topics ## BlogPostProof Understand threats and change Node.js security update: fixed versions 22.23.4, 24.22.1 and 26.12.1 Christophe Henner , Author , 22 Oct 2026 , 4 min read What should I ask my IT team or supplier to do? Update every supported Node.js installation to 22.23.4, 24.22.1 or 26.12.1, matching its major release line. Node.js is behind-the-scenes software used by many websites, online shops and apps. This flaw could let an attacker run their own code on the computer that powers an affected service. Tell your IT team, web developer, software supplier or hosting company about the update. Ask them to check any websites, apps or services they manage, install the matching fix, and confirm when it is done. The fixed versions are 22.23.4 for Node.js 22, 24.22.1 for Node.js 24, and 26.12.1 for Node.js 26. If they find Node.js 20 or older, ask for a plan to upgrade. Node.js security security update runtime patching Jump to Quick answer Match the patch to the runtime What the release fixes Close the gap in production Sources Node.js released security updates on 21 October 2026 for its 22.x, 24.x and 26.x lines. Apply the patch matching each line: 22.23.4, 24.22.1 or 26.12.1. The release fixes four high severity vulnerabilities, including a flaw in the Brotli decoder that the project says permits remote code execution (RCE) 1Reference 1: Wednesday, October 21, 2026 Security Releases. RCE means an attacker may be able to make code run on an affected system. The notice does not describe the exploit conditions or say whether attacks are under way. Patch every live installation instead of trying to infer exposure from the short notice. Think of each Node installation as a separate copy of a door lock: changing the one on a developer’s laptop does not change the lock on the production service. A laptop, build runner, container image, production server and scheduled job can each run a different Node.js binary. Check the environment that actually serves the application. Match the patch to the runtime Node.js 22: 22.23.4 Node.js 24: 24.22.1 Node.js 26: 26.12.1 The node --version command reports the version in the environment where it runs. Check from inside each production container or host, or ask its owner for the deployed runtime version. Updating a project’s packages does not necessarily update the Node.js binary supplied by a container or hosting provider. What the release fixes The Brotli flaw is CVE-2026-111497. The other three high severity issues affect DNS handling and TLS certificate hostname checks. One TLS issue involves IP addresses written with fullwidth digits and affects Node 24 and 26; another involves hostnames that loosely resolve to an IP address, and affects all three lines. Node also fixed DNS handling for names containing a NUL character. The security notice lists additional medium and low severity issues, so deploy the complete release 1Reference 1: Wednesday, October 21, 2026 Security Releases. The update also changes certificates trusted by Node.js. The advisory lists a ca-cert update for all three lines. Mozilla reported that private keys associated with eight eMudhra intermediate certificates had been compromised and could be used to issue fraudulent HTTPS certificates 2Reference 2: Protecting Firefox users following the compromise of eMudhra intermediate certificates. Node 24.22.1’s release notes confirm an update to its root certificate list, to NSS 3.131.1 3Reference 3: Node.js 24.22.1 (LTS). Ask a hosting provider to confirm that its managed runtime includes the certificate update as well as the security fixes. Close the gap in production List the websites, APIs, background jobs and build images that use Node.js. Record the owner and exact version for each. Upgrade supported installations to the matching patch, rebuild and redeploy containers, then verify the version inside the running service and test important customer tasks such as sign-in or payment. If a system still runs Node 20 or an older line, do not wait for a patch number that will not arrive from the Node.js project. End-of-life versions no longer receive project security updates; Node 20 reached end of life on 24 March 2026 1Reference 1: Wednesday, October 21, 2026 Security Releases 4Reference 4: End-Of-Life (EOL). Plan a move to a maintained release and ask the provider for its supported upgrade path. If time is limited, start with the service whose failure would stop sales or essential work. Our small business cyber security guide shows how to trace that work to the systems it depends on. Sources 1. Wednesday, October 21, 2026 Security Releases The Node.js Project Node.js Published 21 Oct 2026 Source language: en Accessed 22 Oct 2026 2. Protecting Firefox users following the compromise of eMudhra intermediate certificates Firefox Security Team Mozilla Security Blog Published 20 Oct 2026 Source language: en Accessed 22 Oct 2026 3. Node.js 24.22.1 (LTS) Antoine du Hamel Node.js Published 21 Oct 2026 Source language: en Accessed 22 Oct 2026 4. End-Of-Life (EOL) Node.js Source language: en Accessed 22 Oct 2026 Page progress 0% You’re here 4 min left On this page Quick answer Match the patch to the runtime What the release fixes Close the gap in production Sources Terms explained Exploit An exploit is code or a method that takes advantage of a security weakness to produce an unintended result. CVE A Common Vulnerabilities and Exposures identifier gives a publicly disclosed security flaw a shared reference across reports and tools. TLS Transport Layer Security (TLS) is a protocol that protects data exchanged between connected systems against interception and tampering. HTTPS HTTPS is the secure form of web communication that encrypts information exchanged between a browser and a website. Cyber security Cyber security is how people, processes and technology protect digital systems, accounts, networks and data from unauthorised access, disruption or misuse. ## BlogPostHeroAnswer What should I ask my IT team or supplier to do? Update every supported Node.js installation to 22.23.4, 24.22.1 or 26.12.1, matching its major release line. Node.js is behind-the-scenes software used by many websites, online shops and apps. This flaw could let an attacker run their own code on the computer that powers an affected service. Tell your IT team, web developer, software supplier or hosting company about the update. Ask them to check any websites, apps or services they manage, install the matching fix, and confirm when it is done. The fixed versions are 22.23.4 for Node.js 22, 24.22.1 for Node.js 24, and 26.12.1 for Node.js 26. If they find Node.js 20 or older, ask for a plan to upgrade. ## ArticleReferencesProof Sources 1. Wednesday, October 21, 2026 Security Releases The Node.js Project Node.js Published 21 Oct 2026 Source language: en Accessed 22 Oct 2026 2. Protecting Firefox users following the compromise of eMudhra intermediate certificates Firefox Security Team Mozilla Security Blog Published 20 Oct 2026 Source language: en Accessed 22 Oct 2026 3. Node.js 24.22.1 (LTS) Antoine du Hamel Node.js Published 21 Oct 2026 Source language: en Accessed 22 Oct 2026 4. End-Of-Life (EOL) Node.js Source language: en Accessed 22 Oct 2026