CVEMETERBack to radar
OFFICIAL RECORD · Node.js

CVE-2026-106069

PUBLISHEDOfficial status check: verifiedCVSS 3.0: 7.4 · high

Node.js · 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**.

Exposure status: unknown. This page does not establish whether an installed system is affected or corrected.

Severity and exploitation evidence

EPSS: 0.304% · score date 2026-11-19. EPSS is an estimated probability over the next 30 days, not proof of exploitation.

CISA KEV: not included in the checked catalog; exploitation may still occur. Last checked: 2026-11-19T18:36:01.564Z. Public exploit availability is not used to set this status.

CVSS 3.0 · 7.4 · published by hackerone
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Assessment source · checked 2026-11-19T10:46:05.061Z

CVSS 3.0 · 7.4 · published by Ubuntu Security
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Assessment source · checked 2026-11-19T18:40:03.310Z

Verification by field

FieldStatusChecked at (UTC)Source
kevverified2026-11-19T18:36:01.564ZCISA KEV
cvssverified2026-11-19T10:46:05.061ZCVE Program
epssverified2026-11-19T18:27:13.977ZFIRST EPSS
patchesunknownunknownunknown
affectedverified2026-11-19T10:46:05.061ZCVE Program
lifecycleverified2026-11-19T10:46:05.061ZCVE Program

Affected versions and configuration

nodejs node; default status: unaffected: 22.23.3 to ≤ 22.23.3 [affected; scheme: semver]; 24.22.0 to ≤ 24.22.0 [affected; scheme: semver]; 26.12.0 to ≤ 26.12.0 [affected; scheme: semver]

Defaults, conditional configuration, package status and version schemes are retained below. A version range alone is not an exposure verdict.

Ubuntu Security · ubuntu-package · full conditions
[
  {
    "name": "nodejs",
    "debian": "https://tracker.debian.org/pkg/nodejs",
    "source": "https://ubuntu.com/security/cve?package=nodejs",
    "ubuntu": "https://packages.ubuntu.com/search?suite=all&section=all&arch=any&searchon=sourcenames&keywords=nodejs",
    "statuses": [
      {
        "pocket": "security",
        "status": "needs-triage",
        "component": null,
        "description": "",
        "release_codename": "trusty"
      },
      {
        "pocket": "security",
        "status": "needs-triage",
        "component": null,
        "description": "",
        "release_codename": "xenial"
      },
      {
        "pocket": "security",
        "status": "needs-triage",
        "component": null,
        "description": "",
        "release_codename": "bionic"
      },
      {
        "pocket": "security",
        "status": "needs-triage",
        "component": null,
        "description": "",
        "release_codename": "focal"
      },
      {
        "pocket": "security",
        "status": "needs-triage",
        "component": null,
        "description": "",
        "release_codename": "jammy"
      },
      {
        "pocket": "security",
        "status": "needs-triage",
        "component": null,
        "description": "",
        "release_codename": "noble"
      },
      {
        "pocket": "security",
        "status": "needs-triage",
        "component": null,
        "description": "",
        "release_codename": "resolute"
      },
      {
        "pocket": "security",
        "status": "needs-triage",
        "component": null,
        "description": "",
        "release_codename": "stonking"
      },
      {
        "pocket": "security",
        "status": "needs-triage",
        "component": null,
        "description": "",
        "release_codename": "upstream"
      }
    ]
  }
]
Archived source JSON
CVE Program · cve-json · full conditions
{
  "affected": [
    {
      "vendor": "nodejs",
      "product": "node",
      "versions": [
        {
          "status": "affected",
          "version": "22.23.3",
          "versionType": "semver",
          "lessThanOrEqual": "22.23.3"
        },
        {
          "status": "affected",
          "version": "24.22.0",
          "versionType": "semver",
          "lessThanOrEqual": "24.22.0"
        },
        {
          "status": "affected",
          "version": "26.12.0",
          "versionType": "semver",
          "lessThanOrEqual": "26.12.0"
        }
      ],
      "defaultStatus": "unaffected"
    }
  ],
  "additionalContainers": [
    {
      "title": "CISA ADP Vulnrichment",
      "metrics": [
        {
          "other": {
            "type": "ssvc",
            "content": {
              "id": "CVE-2026-106069",
              "role": "CISA Coordinator",
              "options": [
                {
                  "Exploitation": "none"
                },
                {
                  "Automatable": "no"
                },
                {
                  "Technical Impact": "total"
                }
              ],
              "version": "2.0.3",
              "timestamp": "2026-11-02T13:30:11.711010Z"
            }
          }
        }
      ],
      "providerMetadata": {
        "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "shortName": "CISA-ADP",
        "dateUpdated": "2026-11-02T13:31:52.012Z"
      }
    }
  ]
}
Archived source JSON

Correction evidence

Distribution packages and upstream releases are distinct. ESM channels may require the corresponding Ubuntu entitlement. Notes and branch ranges are not installable package versions. OSV fixed boundaries are ecosystem-specific version thresholds, not proof that a package is currently available or installed.

No correction has been verified in the connected records. This does not mean the system is secure or that no vendor correction exists.

Vendor notices and operational guidance

No connected vendor notice is available for this record.

Original sources and dates

Official status history