CVE-2026-105481: Node.js vulnerability

Should you act?

Normal patch cycle

No exploitation signal; fix it in your next routine update if you are affected. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog. That can change quickly after a public write-up; re-check if you are affected.
• Editorial verdict: Patch this week. Node.js October 2026 Security Releases: 10 CVEs Fixed — Four high-severity fixes, including a Brotli decoder memory-corruption bug the project says permits remote code execution, make this a routine-but-real upgrade: roll every supported line forward this week.

What it is

The CVE record for this identifier has not been published in full yet. The references below are the best available sources.

Product: Node.js · Published: 2026-10-21

Affected and fixed versions

The CVE record does not list structured version data. Use the vendor advisory in the sources below for exact affected and fixed versions.

Severity scores

No CVSS score has been published for this CVE yet.

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).

Timeline

• 2026-10-21 — erroneo.us brief: Node.js October 2026 Security Releases: 10 CVEs Fixed

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. CVE.org record CVE-2026-105481 cve.org
2. NVD entry CVE-2026-105481 nvd.nist.gov

Today’s Security Digest