Repeated triggering of this condition can lead to denial of service.
This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Tue, 11 Aug 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Node.js dns.resolveAny Denial of Service via Excessive A Records | nodejs: Node.js: Denial of Service via DNS responses with excessive A records |
| Weaknesses | CWE-770 | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Fri, 07 Aug 2026 10:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nodejs
Nodejs nodejs |
|
| Vendors & Products |
Nodejs
Nodejs nodejs |
Tue, 04 Aug 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Node.js dns.resolveAny Denial of Service via Excessive A Records |
Tue, 04 Aug 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 04 Aug 2026 01:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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**. | |
| Weaknesses | CWE-400 | |
| References |
| |
| Metrics |
cvssV3_0
|
Status: PUBLISHED
Assigner: hackerone
Published:
Updated: 2026-08-04T15:03:30.449Z
Reserved: 2026-06-27T15:00:00.780Z
Link: CVE-2026-58042
Updated: 2026-08-04T14:19:37.262Z
Status : Received
Published: 2026-08-04T01:16:20.123
Modified: 2026-08-04T16:16:25.940
Link: CVE-2026-58042
OpenCVE Enrichment
Updated: 2026-08-11T02:15:03Z