{"answers":{"affected":"2 open source packages ship an affected version, including node and node-min. It affects 3 products.","exploited":"There is no known exploitation of CVE-2026-21710 in the wild and no public exploit code.","fix":"Upgrade node to a fixed version for your release line: 20.20.2, 22.22.2, 24.14.1 or 25.8.2.","what":"CVE-2026-21710 is a high-severity denial of service vulnerability in Nodejs Node.js, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-21710 and fix it if it is affected.\n\nWhat it is: CVE-2026-21710 is a high-severity denial of service vulnerability in Nodejs Node.js, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-21710 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- node (Bitnami): affected all versions; fixed in 20.20.2, 22.22.2, 24.14.1, 25.8.2\n- node-min (Bitnami): affected all versions; fixed in 20.20.2, 22.22.2, 24.14.1, 25.8.2\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-21710/ (Markdown: https://insights.sbomify.com/CVE-2026-21710/index.md)","id":"CVE-2026-21710","markdown":"https://insights.sbomify.com/CVE-2026-21710/index.md","name":"CVE-2026-21710","record":{"aliases":["ALPINE-CVE-2026-21710","AZL-81239","AZL-81257","BELL-CVE-2026-21710","BIT-node-2026-21710","BIT-node-min-2026-21710","CLEANSTART-2026-NZ34356","DEBIAN-CVE-2026-21710","ECHO-b7bc-591c-5019","GHSA-xv6w-gxj8-v943","MINI-32gw-w7gv-h9m9","MINI-492r-pc2g-2wg5","MINI-7q5j-jh2h-5hpm","MINI-97jq-gqf8-599q","MINI-cv89-6xw4-w943","MINI-pw39-qm2v-8425","MINI-r7vg-g62m-xr5g","UBUNTU-CVE-2026-21710"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js runtime","requires_auth":"none","summary":"An attacker can crash Node.js HTTP servers by sending a request with a __proto__ header, causing an unhandled TypeError in header processing.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"node.js","vendor":"nodejs"},{"product":"enterprise_linux","vendor":"redhat"},{"product":"enterprise_linux_eus","vendor":"redhat"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"},{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"A flaw in Node.js HTTP request handling causes an uncaught `TypeError` when a request is received with a header named `__proto__` and the application accesses `req.headersDistinct`.\r\n\r\nWhen this occurs, `dest[\"__proto__\"]` resolves to `Object.prototype` rather than `undefined`, causing `.push()` to be called on a non-array. This exception is thrown synchronously inside a property getter and cannot be intercepted by `error` event listeners, meaning it cannot be handled without wrapping every `req.headersDistinct` access in a `try/catch`.\r\n\r\n* This vulnerability affects all Node.js HTTP servers on **20.x, 22.x, 24.x, and v25.x**","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":"2026-04-01","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-04-01T06:02:42Z","kind":"github_poc","ref":"https://github.com/open-flaw/CVE-2026-21710","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":true,"headline":"Denial of service in node","id":"CVE-2026-21710","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"nodejs:node.js","products":["nodejs:node.js","redhat:enterprise_linux","redhat:enterprise_linux_eus"],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Security feature bypass in node","id":"CVE-2026-21711"},"packages":[{"ecosystem":"Bitnami","fixed":["20.20.2","22.22.2","24.14.1","25.8.2"],"introduced":["0","21.0.0","23.0.0","25.0.0"],"last_affected":[],"package":"node","purl":"pkg:bitnami/node","source":"BIT-node-2026-21710"},{"ecosystem":"Bitnami","fixed":["20.20.2","22.22.2","24.14.1","25.8.2"],"introduced":["0","21.0.0","23.0.0","25.0.0"],"last_affected":[],"package":"node-min","purl":"pkg:bitnami/node-min","source":"BIT-node-min-2026-21710"}],"prev":{"headline":"Security feature bypass in Backup and Replication","id":"CVE-2026-21709"},"products":["node"],"published":"2026-03-30","related":[{"cvss_score":9.8,"headline":"Security feature bypass in Node","id":"CVE-2023-32002","kev_date_added":null,"published":"2023-08-21"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2016-6303","kev_date_added":null,"published":"2016-09-16"},{"cvss_score":9.1,"headline":"Security feature bypass in Node.js","id":"CVE-2017-15896","kev_date_added":null,"published":"2017-12-11"},{"cvss_score":8.8,"headline":"Server-side request forgery in Node.js","id":"CVE-2018-7160","kev_date_added":null,"published":"2018-05-17"},{"cvss_score":8.1,"headline":"Misconfiguration in Node.js","id":"CVE-2018-12120","kev_date_added":null,"published":"2018-11-28"},{"cvss_score":7.9,"headline":"Path traversal in Node","id":"CVE-2024-21891","kev_date_added":null,"published":"2024-02-20"},{"cvss_score":7.9,"headline":"Path traversal in Node","id":"CVE-2024-21896","kev_date_added":null,"published":"2024-02-20"}],"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":"US public information, NVD API terms","name":"NVD"},{"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["nodejs"]},"summary":"An attacker can crash Node.js HTTP servers by sending a request with a __proto__ header, causing an unhandled TypeError in header processing.","url":"https://insights.sbomify.com/CVE-2026-21710/"}