CVEMETERBack to radar
OFFICIAL RECORD · Node.js

CVE-2026-123872

PUBLISHEDOfficial status check: verifiedCVSS 3.0: 8.1 · high

Node.js is vulnerable to a client certificate authentication bypass via TLS 1.2 renegotiation servername change

A client certificate authentication bypass in Node.js TLS lets a client change the servername during TLS 1.2 renegotiation to reach endpoints it was not authorized for. On a server that applies different client-certificate policies per hostname, for example stricter admin-only client-cert auth on one host and ordinary client-cert auth on another, a client that authenticates for a permitted host can renegotiate the TLS 1.2 connection under a different servername and carry its existing authentication to the protected host, bypassing the stricter policy. 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.409% · 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 · 8.1 · published by openjs
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Assessment source · checked 2026-11-19T10:46:08.592Z

CVSS 3.0 · 8.1 · published by Ubuntu Security
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Assessment source · checked 2026-11-19T14:19:49.839Z

Verification by field

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

Affected versions and configuration

nodejs node; default status: unaffected: 0.0.0 to < 22.23.5 [affected; scheme: semver]; 23.0.0 to < 24.22.3 [affected; scheme: semver]; 25.0.0 to < 26.13.1 [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": "0.0.0",
          "lessThan": "22.23.5",
          "versionType": "semver"
        },
        {
          "status": "affected",
          "version": "23.0.0",
          "lessThan": "24.22.3",
          "versionType": "semver"
        },
        {
          "status": "affected",
          "version": "25.0.0",
          "lessThan": "26.13.1",
          "versionType": "semver"
        }
      ],
      "defaultStatus": "unaffected"
    }
  ],
  "additionalContainers": [
    {
      "title": "CISA ADP Vulnrichment",
      "metrics": [
        {
          "other": {
            "type": "ssvc",
            "content": {
              "id": "CVE-2026-123872",
              "role": "CISA Coordinator",
              "options": [
                {
                  "Exploitation": "none"
                },
                {
                  "Automatable": "no"
                },
                {
                  "Technical Impact": "total"
                }
              ],
              "version": "2.0.3",
              "timestamp": "2026-11-16T21:44:46.580690Z"
            }
          }
        }
      ],
      "providerMetadata": {
        "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "shortName": "CISA-ADP",
        "dateUpdated": "2026-11-16T21:44:57.995Z"
      }
    }
  ]
}
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