Vulnerability · CVE-2026-105483
A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non
Published Oct 22, 2026 · catalog updated Oct 24, 2026 · A flaw in Node.js
Last checked Oct 31, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-105483. EPSS is 0.30%. Act only if a listed version of A flaw in Node.js is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (A flaw in Node.js).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High7.4
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.30%
- Remediation
- Advisory link
- Affected products
- Alpine:v3.23 nodejs · Alpine:v3.24 nodejs · Debian:12 nodejs · Debian:13 nodejs · Debian:14 nodejs
A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits ( ). did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing or could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618. This vulnerability affects Node.js **26.x** and **24.x**.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Alpine:v3.23 nodejs0 → 24.22.1-r0
- Alpine:v3.24 nodejs0 → 24.22.1-r0
- Debian:12 nodejs18.13.0+dfsg1-1, 18.13.0+dfsg1-1.1, 18.19.0+dfsg-1
- Debian:13 nodejs20.19.2+dfsg-1, 20.19.2+dfsg-1+deb13u1, 20.19.2+dfsg-1+deb13u2
- Debian:14 nodejs20.19.2+dfsg-1, 20.19.4+dfsg-1, 20.19.5+dfsg+~cs20.19.12-1
How to fix CVE-2026-105483
Upgrade
CVE-2026-105483 lists a fix boundary at 24.22.1-r0. Compare the installed build with that boundary before you change production.
Version check
Fixed in 24.22.1-r0 · 10 other ranges on the advisory
Advisory
Open the bsi record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-105483. EPSS is 0.30%. Act only if a listed version of A flaw in Node.js is installed.
Which versions are affected?
Compare what you have installed with 0 → 24.22.1-r0, 18.13.0+dfsg1-1, 18.13.0+dfsg1-1.1, 18.19.0+dfsg-1, 20.19.2+dfsg-1, 20.19.2+dfsg-1+deb13u1, 20.19.2+dfsg-1+deb13u2, 20.19.2+dfsg-1, 20.19.4+dfsg-1, 20.19.5+dfsg+~cs20.19.12-1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.30%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Oct 22, 2026 · Trivy Vulnerability DB
Detected
Oct 22, 2026 · Trivy Vulnerability DB
Updated
The description or metadata changed.
Oct 24, 2026 · Trivy Vulnerability DB
Fix available
nodejs fixed in 24.22.1-r0; nodejs fixed in 24.22.1-r0
Oct 24, 2026 · Trivy Vulnerability DB
Fix available
nodejs fixed in 24.22.1-r0
Oct 24, 2026 · Trivy Vulnerability DB
Updated
A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits ( ). did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Comm
Sources
- BSI CERT-BundGovernment advisoryCVE-2026-105483
Node.js: Mehrere Schwachstellen
wid.cert-bund.de - Cisco Security AdvisoriesVendor advisoryCVE-2026-105483
On October 21, 2026, Node.js announced the availability of fixes for multiple vulnerabilities across the following supported release lines: 22.x, 24.x, and 26.x. These vulnerabilities impact critical operations such as the Brotli decoder, DNS resolution, and TLS certificate valid
sec.cloudapps.cisco.com - CVE.orgVulnerability recordCVE-2026-105483
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-105483
30-day exploitation probability 0.30%
first.org - OpenSSF OSV / OSV ScannerPackage advisoryALPINE-CVE-2026-105483osv.dev
- Trivy Vulnerability DBPackage advisoryALPINE-CVE-2026-105483
A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits ( ). did not recognize such hosts as IP addresses, even
osv.dev - Trivy Vulnerability DBPackage advisoryDEBIAN-CVE-2026-105483osv.dev
- urlscan.ioThreat intelligenceCVE-2026-105483urlscan.io
References
Freshness
Last verified in this catalog Oct 29, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- urlscan.ioOct 31, 2026
- Cisco Security AdvisoriesOct 31, 2026
- BSI CERT-BundOct 31, 2026
- FIRST EPSSOct 29, 2026
- OpenSSF OSV / OSV ScannerOct 25, 2026
- Trivy Vulnerability DBOct 25, 2026
- CVE.orgOct 23, 2026
- Trivy Vulnerability DBOct 23, 2026