{"answers":{"affected":"2 open source packages ship an affected version, including node and node-min.","exploited":"There is no known exploitation of CVE-2026-105483 in the wild and no public exploit code.","fix":"Upgrade node to a fixed version for your release line: 24.22.1 or 26.12.1.","what":"CVE-2026-105483 is a high-severity vulnerability in nodejs node, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-105483 and fix it if it is affected.\n\nWhat it is: CVE-2026-105483 is a high-severity vulnerability in nodejs node, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-105483 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- node (Bitnami): affected from 23.0.0; fixed in 24.22.1, 26.12.1\n- node-min (Bitnami): affected from 23.0.0; fixed in 24.22.1, 26.12.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-105483/ (Markdown: https://insights.sbomify.com/CVE-2026-105483/index.md)","id":"CVE-2026-105483","markdown":"https://insights.sbomify.com/CVE-2026-105483/index.md","name":"CVE-2026-105483","record":{"aliases":["ALPINE-CVE-2026-105483","AZL-111038","BIT-node-2026-105483","BIT-node-min-2026-105483","DEBIAN-CVE-2026-105483","GHSA-8h4p-qpcq-gq24","UBUNTU-CVE-2026-105483"],"analysis":null,"analysis_generated_by":null,"assigner":"hackerone","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"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 (`１２７.0.0.1`).\n\n`tls.checkServerIdentity()` 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 `DNS:127.0.0.1` or `DNS:*.0.0.1` 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.\n\nThis vulnerability affects Node.js **26.x** and **24.x**.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":"2026-10-23","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-23T23:47:01Z","kind":"github_poc","ref":"https://github.com/CompleteTech-Security/node-cve-2026-105483-check","stars":0,"title":"Offline Node.js evidence checker for CVE-2026-105483: TLS fullwidth-IP hostname validation bypass. Single-file Python; JSON/CSV/HTML reports; no exploit payloads."}],"tier":"poc_unverified"},"has_fix":true,"headline":"A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 a","id":"CVE-2026-105483","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":null,"year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"TOTOLINK X6000R UploadFirmwareFile cstecgi.cgi firmware_check os command injection","id":"CVE-2026-105484"},"packages":[{"ecosystem":"Bitnami","fixed":["24.22.1","26.12.1"],"introduced":["23.0.0","25.0.0"],"last_affected":[],"package":"node","purl":"pkg:bitnami/node","source":"BIT-node-2026-105483"},{"ecosystem":"Bitnami","fixed":["24.22.1","26.12.1"],"introduced":["23.0.0","25.0.0"],"last_affected":[],"package":"node-min","purl":"pkg:bitnami/node-min","source":"BIT-node-min-2026-105483"}],"prev":{"headline":"A flaw in Node.js DNS resolution allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*() functions and dns.reverse().","id":"CVE-2026-105482"},"products":["node"],"published":"2026-10-23","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-23","vendors":["nodejs"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-105483/"}