Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

Поиск уязвимостей

Количество 14

Количество 14

ubuntu логотип

CVE-2026-106069

17 дней назад

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 following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

CVSS3: 7.4
EPSS: Низкий
redhat логотип

CVE-2026-106069

20 дней назад

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 following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

CVSS3: 7.4
EPSS: Низкий
nvd логотип

CVE-2026-106069

17 дней назад

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 following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

CVSS3: 7.4
EPSS: Низкий
msrc логотип

CVE-2026-106069

13 дней назад

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 following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

CVSS3: 7.4
EPSS: Низкий
debian логотип

CVE-2026-106069

17 дней назад

A flaw in Node.js TLS hostname verification can cause a server certifi ...

CVSS3: 7.4
EPSS: Низкий
github логотип

GHSA-jj44-m59q-wmrj

17 дней назад

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 following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

CVSS3: 7.4
EPSS: Низкий
suse-cvrf логотип

openSUSE-SU-2026:22210-1

10 дней назад

Security update for nodejs22

EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2026:5036-1

7 дней назад

Security update for nodejs22

EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2026:4957-1

10 дней назад

Security update for nodejs22

EPSS: Низкий
suse-cvrf логотип

SUSE-SU-2026:5037-1

7 дней назад

Security update for nodejs24

EPSS: Низкий
rocky логотип

RLSA-2026:92378

10 дней назад

Important: nodejs:24 security, bug fix, and enhancement update

EPSS: Низкий
rocky логотип

RLSA-2026:92376

11 дней назад

Important: nodejs:24 security, bug fix, and enhancement update

EPSS: Низкий
oracle-oval логотип

ELSA-2026-92378

11 дней назад

ELSA-2026-92378: nodejs:24 security, bug fix, and enhancement update (IMPORTANT)

EPSS: Низкий
oracle-oval логотип

ELSA-2026-92376

11 дней назад

ELSA-2026-92376: nodejs:24 security, bug fix, and enhancement update (IMPORTANT)

EPSS: Низкий

Уязвимостей на страницу

Уязвимость
CVSS
EPSS
Опубликовано
ubuntu логотип
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 following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

CVSS3: 7.4
0%
Низкий
17 дней назад
redhat логотип
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 following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

CVSS3: 7.4
0%
Низкий
20 дней назад
nvd логотип
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 following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

CVSS3: 7.4
0%
Низкий
17 дней назад
msrc логотип
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 following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

CVSS3: 7.4
0%
Низкий
13 дней назад
debian логотип
CVE-2026-106069

A flaw in Node.js TLS hostname verification can cause a server certifi ...

CVSS3: 7.4
0%
Низкий
17 дней назад
github логотип
GHSA-jj44-m59q-wmrj

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 following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

CVSS3: 7.4
0%
Низкий
17 дней назад
suse-cvrf логотип
openSUSE-SU-2026:22210-1

Security update for nodejs22

10 дней назад
suse-cvrf логотип
SUSE-SU-2026:5036-1

Security update for nodejs22

7 дней назад
suse-cvrf логотип
SUSE-SU-2026:4957-1

Security update for nodejs22

10 дней назад
suse-cvrf логотип
SUSE-SU-2026:5037-1

Security update for nodejs24

7 дней назад
rocky логотип
RLSA-2026:92378

Important: nodejs:24 security, bug fix, and enhancement update

10 дней назад
rocky логотип
RLSA-2026:92376

Important: nodejs:24 security, bug fix, and enhancement update

11 дней назад
oracle-oval логотип
ELSA-2026-92378

ELSA-2026-92378: nodejs:24 security, bug fix, and enhancement update (IMPORTANT)

11 дней назад
oracle-oval логотип
ELSA-2026-92376

ELSA-2026-92376: nodejs:24 security, bug fix, and enhancement update (IMPORTANT)

11 дней назад

Уязвимостей на страницу