Skip to main content
Mallory
← Back to News
open-source-dependency-vulnerabilitywidely-deployed-product-advisoryactively-exploited-vulnerabilitygovernment-vulnerability-catalog

Node.js Plans High-Severity Security Fixes for 22.x, 24.x and 26.x

Active Exploitation · 5 sources · Updated 10d ago · First seen Nov 4, 2026

Node.js Plans High-Severity Security Fixes for 22.x, 24.x and 26.x

The Node.js project has scheduled security updates for its maintained 22.x, 24.x and 26.x release lines on or shortly after November 11, 2026, with each branch receiving a fix for at least one high-severity vulnerability. The advance notice does not disclose CVE identifiers, affected components, technical attack details or fixed version numbers. As of November 4, no exploitation of these forthcoming vulnerabilities has been publicly confirmed.

The planned releases are separate from October’s security updates, which addressed ten vulnerabilities, including CVE-2026-111497, the bundled Brotli decoder flaw known as Node2Shell that could enable memory corruption and remote code execution. Cyberattaque reports that the UK NHS cybersecurity center flagged exploitation attempts against that earlier flaw and that CISA added it to its Known Exploited Vulnerabilities catalog. Administrators should ensure existing patches are installed, inventory deployed Node.js runtimes, prepare to test and deploy the November updates when available, and migrate unsupported versions to a maintained branch.

This is being exploited nowSee which actors are running it and whether you're in range.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

5 events · Oct 21, 2026 – Nov 3, 2026
  1. Reported Nov 4, 202613d ago

    CISA reportedly adds Node2Shell to its Known Exploited Vulnerabilities catalog

    CISA reportedly added CVE-2026-111497 to its Known Exploited Vulnerabilities catalog. The source does not specify when the addition occurred.

    Node.js : les correctifs de ces nouvelles failles ne sont pas attendus avant le 11 novembre
  2. Reported Nov 4, 202613d ago

    UK NHS cybersecurity center reportedly identifies Node2Shell exploitation attempts

    The UK NHS national cybersecurity center reportedly identified exploitation attempts against CVE-2026-111497. These reports concern the previously patched Brotli decoder vulnerability, not the undisclosed vulnerabilities covered by the November advisory.

    Node.js : les correctifs de ces nouvelles failles ne sont pas attendus avant le 11 novembre
  3. Nov 3, 202615d ago

    Node.js announces forthcoming high-severity security updates for three branches

    The Node.js security team published an advisory announcing updates for branches 22.x, 24.x, and 26.x, targeted for November 11, 2026, or shortly afterward. Each branch would receive at least one HIGH-severity fix, but the notice did not disclose CVEs, affected components, fixed versions, or confirmed exploitation.

    Node.js Schedules High-Severity Security Fixes for 22.x, 24.x, and 26.x Release Lines
  4. Oct 28, 202621d ago

    Node.js 26 becomes a long-term support release

    Node.js 26 became a long-term support release on October 28, joining the still-supported Node.js 24 and 22 branches.

    Node.js : les correctifs de ces nouvelles failles ne sont pas attendus avant le 11 novembre
  5. Oct 21, 202628d ago

    Node.js releases fixes for ten vulnerabilities, including Node2Shell

    Node.js released security updates addressing ten vulnerabilities, including four rated HIGH, on October 21. The updates fixed the Brotli decoder flaw CVE-2026-111497, known as Node2Shell, in versions 22.23.4, 24.22.1, and 26.12.1; the flaw could cause memory corruption and potentially remote code execution.

    Node.js Schedules High-Severity Security Fixes for 22.x, 24.x, and 26.x Release Lines
Do you run this?Correlate live exploitation activity against the software you actually run, and see where you're exposed.
See Who's Exploiting This
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.