314 matches found
CVE-2025-46408
CVE-2025-46408 Improper Hostname Verification in EagleEyes Lite Android Application 1. Overview Name : EagleEyesLite Version : 2.0.0 Vendor : AVTECH CWE : CWE-297: Improper Validation of Certificate with Host Mismatch CVSS : 9.8 CRITICAL Vector String : CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:...
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-105483
A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits 127.0.0.1. tls.checkServerIdentity did not recognize such hosts as IP...
CVE-2026-105483
A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits 127.0.0.1. tls.checkServerIdentity did not recognize such hosts as IP...
CVE-2026-105483
A flaw in Node.js TLS hostname verification allows an attacker to bypass certificate validation by using non-ASCII fullwidth digits (e.g., 127.0.0.1) to represent an IP address. The tls.checkServerIdentity() function fails to recognize these as IP addresses, instead matching them against DNS name...
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,...
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-105483
A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits 127.0.0.1. tls.checkServerIdentity did not recognize such 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-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-109100
A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits 127.0.0.1. tls.checkServerIdentity did not recognize such 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-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-105483
A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits 127.0.0.1. tls.checkServerIdentity did not recognize such hosts as IP...
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
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...
PT-2026-120762
A flaw in Node.js crypto causes the internal entropy caches used by crypto.randomUUID, crypto.randomUUIDv7, and crypto.randomInt to be saved into user-land startup snapshots --build-snapshot and single executable applications built with useSnapshot. If any of these functions, or an API that relie...