PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-58042 nodejs CVE debrief

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. The vulnerability is caused by a flaw in Node.js that can cause dns.resolveAny() to abort the Node.js process when a DNS response contains more than 256 A records. This can lead to a denial of service. Node.js administrators and users who rely on Node.js for their applications should be aware of this vulnerability and take necessary actions to mitigate it. The CVE record and NVD entry provide limited information about the vulnerability. Further investigation is needed to determine the full scope of the vulnerability and affected systems.

Vendor
nodejs
Product
node
CVSS
MEDIUM 5.9
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-04
Original CVE updated
2026-09-03
Advisory published
2026-08-04
Advisory updated
2026-09-03

Who should care

Node.js administrators and users who rely on Node.js for their applications should be aware of this vulnerability and take necessary actions to mitigate it. This includes verifying Node.js versions, monitoring systems, and applying patches as available. Security teams should prioritize this vulnerability based on its potential impact on Node.js deployments.

Technical summary

The vulnerability is caused by a flaw in Node.js that can cause dns.resolveAny() to abort the Node.js process when a DNS response contains more than 256 A records. This can lead to a denial of service. The vulnerability affects Node.js versions 26.x, 24.x, and 22.x. Node.js administrators and users who rely on Node.js for their applications should be aware of this vulnerability and take necessary actions to mitigate it.

Defensive priority

Medium-priority defensive actions are required to address this vulnerability.

Recommended defensive actions

  • Inventory Node.js installations and verify versions 26.x, 24.x, and 22.x are up-to-date.
  • Implement compensating controls to detect and prevent denial of service attacks.
  • Monitor Node.js systems for abnormal dns.resolveAny() activity.
  • Verify vendor remediation and apply patches as available.
  • Review Node.js configurations and consider restricting dns.resolveAny() usage.
  • Perform a thorough review of Node.js systems for potential exposure.
  • Track Node.js security advisories for future updates on this vulnerability.

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability. Further investigation is needed to determine the full scope of the vulnerability and affected systems. Node.js administrators should verify their deployments, especially versions 26.x, 24.x, and 22.x, and monitor for abnormal dns.resolveAny() activity. Evidence is limited, and defenders should focus on vendor guidance and compensating controls.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-58042 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-58042

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-58042 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-58042

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.