A flaw in Node.js can cause dns.resolveAny() Aborts the Node.js Process When a DNS Response Contains More Than 256 A Records. Repeated triggering of this condition can lead to denial of service. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade nodejsUpgrade nodejs-current | Aug 5, 2026 | Aug 4, 2026 |
| Amazon_linux_2023 | — | Upgrade nodejs24-full-i18nUpgrade nodejs24-debugsourceUpgrade nodejs22-npmUpgrade nodejs22-develUpgrade nodejs22-docsUpgrade nodejs24-libs-debuginfoUpgrade nodejs24-docsUpgrade nodejs24-libsUpgrade nodejs22-libsUpgrade v8-12.4-develUpgrade nodejs22-debugsourceUpgrade nodejs24-develUpgrade v8-13.6-develUpgrade nodejs22-debuginfoUpgrade nodejs22Upgrade nodejs22-libs-debuginfoUpgrade nodejs22-full-i18nUpgrade nodejs24-npmUpgrade nodejs24-debuginfoUpgrade nodejs24 | Aug 18, 2026 | Aug 4, 2026 |
| Debian | — | Upgrade nodejs | Sep 30, 2026 | Aug 4, 2026 |
| Redhat_linux | — | No solution exists | Aug 12, 2026 | Aug 4, 2026 |
| Vmware Photon_os | — | Use 'tdnf update' to upgrade all packages to the latest version. | Oct 13, 2026 | Aug 4, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub