CVE-2026-106072

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...

CVE-2026-106069

A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as 0127.0.0.1. tls.checkServerIdentity normalizes the host...

CVE-2026-106069

A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as 0127.0.0.1. tls.checkServerIdentity normalizes the host...

CVE-2026-106072

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...

CVE-2026-106069

A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as 0127.0.0.1. tls.checkServerIdentity normalizes the host...

CVE-2026-106069

A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as 0127.0.0.1. tls.checkServerIdentity normalizes the host...

CVE-2026-106072

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...

EUVD-2026-109102

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...

EUVD-2026-109107

A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as 0127.0.0.1. tls.checkServerIdentity normalizes the host...

CVE-2026-106072

A flaw in Node.js TLS hostname verification allows certificates with only a DNS SAN to authenticate an IP endpoint when using non-canonical IPv4 spellings (e.g., 0177.0.0.1, 0x7f.0.0.1, 2130706433, or 127.1). The tls.checkServerIdentity() function fails to classify these as IP addresses, normaliz...

CVE-2026-106069

A flaw in the Node.js TLS hostname verification allows an attacker to bypass security by presenting a certificate for an endpoint that does not belong to them. The tls.checkServerIdentity() function incorrectly normalizes non-canonical IPv4 literals with leading zeros (e.g., 0127.0.0.1) as octal,...

Hitachi Pentaho Business Analytics Server - Bypass Authorization

Hitachi Vantara Pentaho Business Analytics Server versions before 9.4.0.1 and 9.3.0.2, including 8.3.x contain security restrictions using non-canonical URLs which can be circumvented. id: CVE-2022-43939 info: name: Hitachi Pentaho Business Analytics Server - Bypass Authorization author: daffainf...

EUVD-2026-107635

As part of Cisco's ongoing commitment to proactive security and product quality, Cisco has conducted a comprehensive internal security review. This review resulted in a software hardening release that addresses multiple internally discovered vulnerabilities. The vulnerabilities tracked by...

CVE-2026-76530

As part of Cisco's ongoing commitment to proactive security and product quality, Cisco has conducted a comprehensive internal security review. This review resulted in a software hardening release that addresses multiple internally discovered vulnerabilities. The vulnerabilities tracked by...

CVE-2026-76530 Use of Non-Canonical URL Paths for Authorization Decisions in Splunk SOAR

As part of Cisco's ongoing commitment to proactive security and product quality, Cisco has conducted a comprehensive internal security review. This review resulted in a software hardening release that addresses multiple internally discovered vulnerabilities. The vulnerabilities tracked by...

CVE-2026-76530

This vulnerability affects Splunk SOAR and is caused by the use of non-canonical URL paths for authorization decisions, categorized under CWE-647 . Cisco identified this issue during an internal security review and released a software hardening update to address it. The vulnerability has a HIGH b...

Node.js < 22.23.4, < 24.22.1, < 26.12.1 - Improper Certificate Validation for Non-Canonical IPv4 Hostnames

Improper Certificate Validation for Non-Canonical IPv4 Hostnames vulnerability discovered by br41ny in WordPress npm Node.js versions 22.23.4...

Node.js < 22.23.4, < 24.22.1, < 26.12.1 - Improper Certificate Validation via Non-Canonical IP Hostnames

Improper Certificate Validation via Non-Canonical IP Hostnames vulnerability discovered by anagnorisis2peripeteia in WordPress npm Node.js versions 22.23.4...

CVE-2026-106069

Node.js tls.checkServerIdentity normalizes non-canonical numeric hosts e.g. 0127.0.0.1 with domainToASCII before matching the certificate, while the platform resolver connects to a different address, allowing a TLS hostname check bypass. Fixed in 22.23.4, 24.22.1 and 26.12.1...

kin-openapi: Unauthenticated panic (DoS) in openapi3filter legacy router via non-canonical/unsupported HTTP method on a static path

Summary The openapi3filter.ValidationHandler the exported, documented request-validation middleware hard-wires the legacy router routers/legacy. That router matches the incoming request method verbatim against a trie built exclusively from upper-cased canonical HTTP methods. A request carrying a...