{"answers":{"affected":"2 open source packages ship an affected version, including node and node-min.","exploited":"There is no known exploitation of CVE-2026-105482 in the wild and no public exploit code.","fix":"Upgrade node to a fixed version for your release line: 22.23.4, 24.22.1 or 26.12.1.","what":"CVE-2026-105482 is a high-severity vulnerability in nodejs node, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-105482 and fix it if it is affected.\n\nWhat it is: CVE-2026-105482 is a high-severity vulnerability in nodejs node, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-105482 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- node (Bitnami): affected all versions; fixed in 22.23.4, 24.22.1, 26.12.1\n- node-min (Bitnami): affected all versions; fixed in 22.23.4, 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-105482/ (Markdown: https://insights.sbomify.com/CVE-2026-105482/index.md)","id":"CVE-2026-105482","markdown":"https://insights.sbomify.com/CVE-2026-105482/index.md","name":"CVE-2026-105482","record":{"aliases":["ALPINE-CVE-2026-105482","AZL-111035","BIT-node-2026-105482","BIT-node-min-2026-105482","DEBIAN-CVE-2026-105482","GHSA-4qmx-59c6-fr6r","UBUNTU-CVE-2026-105482"],"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-284","name":"Improper Access Control"}],"description":"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(). This is an incomplete fix of CVE-2026-48930, which only covered dns.lookup() and the net/tls host options.\r\n\r\nBecause the name is passed to c-ares as a C string, resolving attacker.example\\0.trusted.example queries attacker.example and returns its records without any error. Applications that validate a hostname, for example against a domain allowlist, and then resolve it with dns.resolve*() can act on records for a different name than the one they validated.\r\n\r\nThis vulnerability affects Node.js 26.x, 24.x, and 22.x.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":"2026-10-21","github_poc":3,"max_poc_stars":9,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-21T15:41:53Z","kind":"github_poc","ref":"https://github.com/CaterMaoZi/CVE-2026-105482-POC","stars":9,"title":"Nodejs漏洞 CVE-2026-105482 POC"},{"date":"2026-10-23T23:46:49Z","kind":"github_poc","ref":"https://github.com/CompleteTech-Security/node-cve-2026-105482-check","stars":0,"title":"Offline Node.js evidence checker for CVE-2026-105482: DNS resolution NUL-name truncation. Single-file Python; JSON/CSV/HTML reports; no exploit payloads."},{"date":"2026-10-28T01:06:08Z","kind":"github_poc","ref":"https://github.com/EthanTech-Offical/CVE-2026-105482-Reproduce","stars":0,"title":"CVE-2026-105482漏洞复现"}],"tier":"poc_unverified"},"has_fix":true,"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","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":null,"year":"2026"},"n_packages":2,"n_references":1,"next":{"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"},"packages":[{"ecosystem":"Bitnami","fixed":["22.23.4","24.22.1","26.12.1"],"introduced":["0","23.0.0","25.0.0"],"last_affected":[],"package":"node","purl":"pkg:bitnami/node","source":"BIT-node-2026-105482"},{"ecosystem":"Bitnami","fixed":["22.23.4","24.22.1","26.12.1"],"introduced":["0","23.0.0","25.0.0"],"last_affected":[],"package":"node-min","purl":"pkg:bitnami/node-min","source":"BIT-node-min-2026-105482"}],"prev":{"headline":"A flaw in Node.js HTTP Agent connection reuse can cause a client to accept as valid a response that was sent before the client has sent the request.","id":"CVE-2026-105481"},"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-105482/"}