CVE-2026-58042
Received Received - Intake

DNS Response Handling Denial of Service in Node.js

Publication date: 2026-08-04

Last updated on: 2026-08-04

Assigner: HackerOne

Description
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**.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-04
Last Modified
2026-08-04
Generated
2026-08-04
AI Q&A
2026-08-04
EPSS Evaluated
N/A
NVD
CVE-2026-58042
EUVD
EUVD-2026-52553

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
nodejs node.js From 26.x (inc)
nodejs node.js From 24.x (inc)
nodejs node.js From 22.x (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-400 The product does not properly control the allocation and maintenance of a limited resource.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a flaw in Node.js where the dns.resolveAny() function aborts the Node.js process if a DNS response contains more than 256 A records. Repeated exploitation can cause a denial of service by crashing the application.

Detection Guidance

This vulnerability can be detected by monitoring Node.js processes for crashes when handling DNS responses with more than 256 A records. Check Node.js logs for abnormal terminations or use process monitoring tools like 'pm2' or 'systemd' to track crashes. No specific commands are provided in the context.

Impact Analysis

This vulnerability can impact you by causing unexpected crashes of your Node.js applications, leading to service disruptions. If exploited repeatedly, it may result in a denial of service, making your services unavailable.

Compliance Impact

This vulnerability could potentially impact compliance with GDPR and HIPAA by enabling denial-of-service attacks that disrupt Node.js services handling sensitive data. Repeated exploitation may lead to service unavailability, which could violate availability requirements in these regulations.

Mitigation Strategies

Upgrade Node.js to a patched version that fixes the flaw in dns.resolveAny() handling of DNS responses with more than 256 A records. Avoid using Node.js versions 26.x, 24.x, and 22.x until the update is applied.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-58042. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart