CVE-2026-48928: A inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups.

Routine

MEDIUM 5.4DOWNGRADE

CVE-2026-48928 is a medium-severity flaw (CVSS 5.4) affecting node.js. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 88%)
CISA exploited list	No
Weakness	CWE-284
Published	2026-06-26
Last modified	2026-10-25

Publisher (CNA): HackerOne · Vendor: nodejs

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-26 02:16 UTCPublished CVE record published
2026-10-25 22:10 UTCUpdated Record last modified

nodejs node.js DOWNGRADE

Affected: 22.22.3 · 24.16.0 · 26.3.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 22.22.3

1. Check installed version

apt-cache policy node.js || rpm -q node.js || node.js --version

2. No fixed release: DOWNGRADE to a release before 22.22.3 (Debian / Ubuntu)

apt-cache madison node.js sudo apt install node.js=<VERSION_BEFORE_22.22.3> sudo apt-mark hold node.js

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list node.js sudo dnf downgrade node.js-<VERSION_BEFORE_22.22.3> sudo dnf versionlock add node.js

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-48928?

node.js: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2026-48928 being exploited?

CVE-2026-48928 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-48928 affect?

CVE-2026-48928 affects node.js. Severity is medium (CVSS 5.4). A inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.

How urgent is CVE-2026-48928?

Priority 22/100. No elevated risk signals yet.

Software pages

Node.js vulnerabilities

Related CVEs

CVE-2026-48937 HIGH 7.5 UPGRADE A flaw in Node.js HTTP/2 server API can cause servers to keep accepting data even after sending a `GOAWAY` fra
CVE-2026-48931 LOW 3.7 DOWNGRADE A flaw in Node.js HTTP Agent can cause a client to accept as valid a response that is send before the client h
CVE-2026-48933 HIGH 7.5 DOWNGRADE A flaw in Node.js WebCrypto implementation can crash the process if the input of `subtle.encrypt()` is a multi
CVE-2026-48618 MEDIUM 6.5 DOWNGRADE A flaw in Node.js TLS hostname handling can cause Node.js unicode dot separator handling can lead to tls wildc
CVE-2026-48930 CRITICAL 9.8 DOWNGRADE A flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebindin

References

← Back to latest CVEs