VulnerabilityBSI CERT-Bund
Node.js: Mehrere Schwachstellen
NEOSEC enrichment — no mirror of the original source
Ein Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um einen Denial of Service Angriff durchzuführen, um Sicherheitsvorkehrungen zu umgehen und um beliebigen Programmcode auszuführen.
Source: BSI CERT-Bund. For licensing reasons NEOSEC Intel does not mirror the full text verbatim. The full text and expert commentary are available at the original source.
Read the issue at BSI CERT-BundFull advisory
Criticalbsi:WID-SEC-2026-411710 linked CVEs
Open advisory with all CVEs
More on Node.js
Other advisories
- CriticalCVE-2026-44267Elo JavaScript emitter has sandbox escape to arbitrary Node.js / browser code execution via unfiltered `.constructor` member access
- HighCVE-2026-119179MongoDB Node.js Driver: Sicherheitslücke
- HighCVE-2026-119179MongoDB Node.js Driver: Sicherheitslücke
- CriticalCVE-2026-106071Node.js: Mehrere Schwachstellen
- HighCVE-2026-48619Node.js: Mehrere Schwachstellen
- HighCVE-2026-21716Node.js: Mehrere Schwachstellen
- CriticalCVE-2026-105481A flaw in Node.js HTTP Agent connection reuse can cause a client to accept as valid a response that was sent before the client has sent the request. This is an incomplete fix of CVE-2026-48931. The guard that destroys idle keep-alive sockets when unexpected data arrives only runs when the event loop polls for I/O. If an unsolicited response has already reached the socket but has not been read yet when the socket is handed to a new request, for example because the event loop was busy with synchronous work, the guard is removed without seeing it and the data is parsed as the response to the new request. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
- CriticalCVE-2026-106072A flaw in Node.js TLS hostname verification allows a certificate with only a DNS SAN to authenticate an IP endpoint when the client connects using a non-canonical IPv4 spelling, such as `0177.0.0.1`, `0x7f.0.0.1`, `2130706433` or `127.1`. `tls.checkServerIdentity()` did not classify these hosts as IP addresses, but normalized them to their canonical form and matched the result against the certificate DNS names. A certificate containing `DNS:127.0.0.1` and no `IP Address:127.0.0.1` SAN was therefore accepted, while the same certificate is correctly rejected for `127.0.0.1`. Exploitation requires a certificate with a numeric DNS SAN issued by a CA trusted by the client, and a platform resolver that accepts these spellings, such as glibc. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
Other news entries
- Vulnerabilities in Node.js Affecting Cisco Products: October 2026NewsCisco PSIRT
- A quiet week in infosec <.<NewsCisco Talos
- Node.js: Mehrere SchwachstellenVulnerabilityBSI CERT-Bund
- Node2Shell puts Microsoft and Node.js on Brotli patch dutyNewsCSO Online
- CVE-2026-111497: Critical out-of-bounds write in the Node.js Brotli decoderNewsRapid7
- Critical 'HTTP2Shell' Brotli vulnerability triggers emergency patchesNewsBleepingComputer
- Node2Shell: Brotli Flaw Triggers Patching Across Microsoft, Node.js, Python PackagesNewsSecurityWeek
- Node2Shell CVEsNewsFortinet PSIRT
Source: https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-4117
ID