p PatchFirst

ALPINE-CVE-2026-106069

ALPINE-CVE-2026-106069

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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

CVSS 7.4 · High · Fix available

Published
Updated

Stack: system

Affected products and versions

  • nodejs Alpine:v3.21

    Affected ranges
    • ECOSYSTEM: < 22.23.4-r0

    Update to 22.23.4-r0

  • nodejs Alpine:v3.22

    Affected ranges
    • ECOSYSTEM: < 22.23.4-r0

    Update to 22.23.4-r0

  • nodejs Alpine:v3.23

    Affected ranges
    • ECOSYSTEM: < 24.22.1-r0

    Update to 24.22.1-r0

  • nodejs Alpine:v3.24

    Affected ranges
    • ECOSYSTEM: < 24.22.1-r0

    Update to 24.22.1-r0

Original sources

Check your server →