Summary
Node.js is software widely used behind websites, web services, and apps. The Node.js Project has released updates fixing ten (10) vulnerabilities (security weaknesses) in October 2026. By severity, 4 are High, 3 are Medium, and 3 are Low.
Of particular concern is CVE-2026-111497 (CVSS 4.0 score 9.2: Critical). There is a flaw in Brotli, a compression feature that makes data smaller. If specially crafted data is processed, an attacker may be able to run malicious programs remotely. Web services and apps that process compressed data received from external sources may be affected.
In addition, there are flaws related to verifying communication partners, which may cause a connection to a different destination than intended to be mistakenly judged as legitimate.
These vulnerabilities are mainly addressed by those who operate or develop websites and apps, by updating Node.js.
If you receive a notice from the operator of a service you use, please follow its instructions.
Patched Node.js Versions
Updates resolve all ten issues. Verify running versions with node -v and patch CI images and applications.
| Release line | Patched version |
|---|---|
| 26.x | v26.12.1 |
| 24.x | v24.22.1 |
| 22.x | v22.23.4 |
CVE overview
Full per-CVE details, vectors and affected release lines are in the Node.js advisory and NVD records:
| CVE ID | Title (one line) | CVSS | Severity |
|---|---|---|---|
| CVE-2026-111497 | Brotli decoder out-of-bounds write → RCE (zlib) | 9.2 (v4.0) | High / Critical |
| CVE-2026-105482 | DNS names with NUL bytes silently truncated (dns/c-ares) | 7.4 | High |
| CVE-2026-105483 | TLS hostname bypass via fullwidth-digit IPs (tls) | 7.4 | High |
| CVE-2026-106069 | TLS cert validated against wrong IP (leading-zero host) | 7.4 | High |
| CVE-2026-106072 | DNS SANs authenticate non-canonical IPv4 endpoints (tls) | 6.7 | Medium |
| CVE-2026-105481 | Keep-alive socket accepts unsolicited pre-request response (http) | 6.5 | Medium |
| CVE-2026-106074 | randomUUID()/randomInt() entropy baked into snapshots/SEAs (crypto) | 4.8 | Medium |
| CVE-2026-106070 | zlib.ZipFile returns attacker-controlled bytes on ZIP failure | 3.7 | Low |
| CVE-2026-106071 | Permission Model filesystem over-grant via wildcard lookup | 3.6 | Low |
| CVE-2026-106073 | Permission Model bypass via fs.realpathSync() | 3.3 | Low |
CVSS values are NVD vendor/secondary scores as of 2026-10-26; all records are currently "Awaiting Analysis" and may be revised. Node.js itself does not publish numeric CVSS scores — publisher Google rates CVE-2026-111497 at 9.2 (Critical), while Node labels it High.
Recommended Actions
Those who operate or develop websites and apps
- Update Node.js immediately
Update to the patched release for your version — v26.12.1, v24.22.1, or v22.23.4. This is the only complete mitigation. You can check the running version with node -v. - Prioritize the Brotli (compression feature) vulnerability (CVE-2026-111497)
Identify apps that process compressed data received from external sources and patch them first. If you bundle Brotli on its own, update to 1.0.10, 1.1.1, or 1.2.1. - Check whether you use features related to verifying communication partners or permission settings
The relevant features are hostname and IP address verification, DNS allowlists, keep-alive connections, deployments using --permission, and random value (such as UUID) generation. - Move versions that have reached end of support (EOL) to a supported version
Follow the Node.js release schedule.
General users: What you should do
These vulnerabilities are mainly addressed by those who operate or develop websites and apps, but it is also important for general users to keep their devices up to date.
- Keep your OS, browser, and apps up to date
Loading malicious data prepared by an attacker (data compressed with Brotli) may allow your device to be operated without your permission. If updates are available, apply them right away.- Update your web browser
Update browsers such as Google Chrome, Microsoft Edge, Apple Safari, and Mozilla Firefox to the latest version, and restart the browser. - Update your OS
If system updates (security patches) for Windows, macOS, iOS, or Android are available, apply them right away. - Update the apps you use every day
Apps that include web technology, like chat tools (Slack, Discord, etc.), should also be updated promptly. If you are a developer, also update tools such as Git for Windows.
- Update your web browser
- Be vigilant against scammers
Fake text messages and emails that take advantage of news about vulnerabilities may be sent. If you receive a message claiming a security issue and directing you to a link, don't click it right away. Go directly to the company's official site, or contact the company another way to verify. - Check for notices from the services you use
If an organization that operates a service you use tells you it was impacted by this issue, follow its instructions and change your password. - Use security products
Trend Micro ScamCheck can help you verify suspicious messages. Trend Micro Mobile Security (Android or iOS) or Trend Micro Maximum Security (laptops and desktops) can help keep you safe.
Impact on TrendLife Products and Services
TrendLife has implemented an urgent assessment of existing TrendLife products and services that may be impacted by these vulnerabilities. More information will be shared in a separate article if any TrendLife products are affected and the necessary mitigation steps needed to address.
TrendAI Impacted Products and Services
For information about TrendAI products, please refer to https://success.trendmicro.com/en-US/solution/KA-0024830
