CVE-2026-106072
Node.js server spoofing via flawed TLS hostname checks
An attacker can impersonate a server and intercept traffic by presenting a certificate that is wrongly trusted.
Texto original en inglés · Ver en español
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-106072 divulgada · CVSS 6.7 (CNA) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Monitoreo | Fuente: ENISA EUVD | Registro visto por primera vez en ENISA EUVD | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación ninguna | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Fuente: PoC-in-GitHub | Registro visto por primera vez en PoC-in-GitHub | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Node.js (versions 22.x, 24.x, and 26.x) is affected through its TLS hostname verification in `tls.checkServerIdentity()`, which can wrongly accept a certificate containing only a numeric DNS name as valid for an IP address written in an unusual format. This could allow a client to be tricked into trusting a server it should reject, potentially enabling man-in-the-middle attacks.
Descripción original del registro (hackerone)
A 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**.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
node |
Sin parche | — | — | — |
Arsenal público
Ver los 1 repositorios de GitHub
Los repositorios públicos incluyen exploits, escáneres, laboratorios y reglas de detección. No ejecute código de terceros sin revisarlo en un entorno aislado.
https://nodejs.org/en/blog/vulnerability/october-2026-security-releaseshttps://github.com/CompleteTech-Security/node-cve-2026-106072-checkLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
