{"answers":{"affected":"2 open source packages ship an affected version, including node and node-min.","exploited":"There is no known exploitation of CVE-2026-106069 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-106069 is a high-severity vulnerability in nodejs node, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-106069 and fix it if it is affected.\n\nWhat it is: CVE-2026-106069 is a high-severity vulnerability in nodejs node, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-106069 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-106069/ (Markdown: https://insights.sbomify.com/CVE-2026-106069/index.md)","id":"CVE-2026-106069","markdown":"https://insights.sbomify.com/CVE-2026-106069/index.md","name":"CVE-2026-106069","record":{"aliases":["ALPINE-CVE-2026-106069","AZL-111047","BIT-node-2026-106069","BIT-node-min-2026-106069","DEBIAN-CVE-2026-106069","GHSA-jj44-m59q-wmrj","UBUNTU-CVE-2026-106069"],"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 can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as `0127.0.0.1`.\n\n`tls.checkServerIdentity()` normalizes the host following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address.\n\nThis vulnerability affects Node.js **26.x**, **24.x**, and **22.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:14Z","kind":"github_poc","ref":"https://github.com/CompleteTech-Security/node-cve-2026-106069-check","stars":0,"title":"Offline Node.js evidence checker for CVE-2026-106069: TLS leading-zero IPv4 resolver mismatch. 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 can cause a server certificate to be validated against a different IP address than the one the c","id":"CVE-2026-106069","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 the Node.js `zlib.ZipFile` API can cause it to return bytes that do not belong to the requested entry after the local and central","id":"CVE-2026-106070"},"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-106069"},{"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-106069"}],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2026-106068"},"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-106069/"}