CVE-2026-58042: A flaw in Node.js can cause dns.resolveAny() Aborts the Node.js Process When a DNS Response Contains More Than 256 A Records.
Noroxi assessment
Priority: Monitor (action score 23/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: nodejs (AlmaLinux:10) 1:22.23.2-1.el10_2; nodejs-devel (AlmaLinux:10) 1:22.23.2-1.el10_2; nodejs-docs (AlmaLinux:10) 1:22.23.2-1.el10_2.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to nodejs (AlmaLinux:10) 1:22.23.2-1.el10_2; nodejs-devel (AlmaLinux:10) 1:22.23.2-1.el10_2; nodejs-docs (AlmaLinux:10) 1:22.23.2-1.el10_2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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**.
- ALSA-2026:61376
- ALSA-2026:61377
- ALSA-2026:61383
- ALSA-2026:61386
- ALSA-2026:62219
- ALSA-2026:62583
- openSUSE-SU-2026:11439-1
- openSUSE-SU-2026:11440-1
- openSUSE-SU-2026:21545-1
- openSUSE-SU-2026:21546-1
- RHSA-2026:48305
- RHSA-2026:48537
- RHSA-2026:52990
- RHSA-2026:61376
- RHSA-2026:61377
- RHSA-2026:61383
- RHSA-2026:61386
- RHSA-2026:62219
- RHSA-2026:62416
- RHSA-2026:62583
- Published
- Aug 4, 2026
- Updated
- Oct 23, 2026
- EPSS
- 0.4% · 36th percentile
- CWE
- CWE-400
Report tools
Action score
23
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · hackerone
- 5.9
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Using node? Add it to your stack and be the first to know about CVEs like this one. (Node.js)
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.
nodejs node
- 26.5.0 and later · up to and including 26.5.0affected · semver
- 24.18.0 and later · up to and including 24.18.0affected · semver
- 22.23.1 and later · up to and including 22.23.1affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | nodejs | before 1:22.23.2-1.el10_2 | 1:22.23.2-1.el10_2 |
| AlmaLinux:10 | nodejs-devel | before 1:22.23.2-1.el10_2 | 1:22.23.2-1.el10_2 |
| AlmaLinux:10 | nodejs-docs | before 1:22.23.2-1.el10_2 | 1:22.23.2-1.el10_2 |
| AlmaLinux:10 | nodejs-full-i18n | before 1:22.23.2-1.el10_2 | 1:22.23.2-1.el10_2 |
| AlmaLinux:10 | nodejs-libs | before 1:22.23.2-1.el10_2 | 1:22.23.2-1.el10_2 |
| AlmaLinux:10 | nodejs-npm | before 1:10.9.8-1.22.23.2.1.el10_2 | 1:10.9.8-1.22.23.2.1.el10_2 |
| AlmaLinux:10 | nodejs24 | before 1:24.19.0-1.el10_2 | 1:24.19.0-1.el10_2 |
| AlmaLinux:10 | nodejs24-devel | before 1:24.19.0-1.el10_2 | 1:24.19.0-1.el10_2 |
| AlmaLinux:10 | nodejs24-docs | before 1:24.19.0-1.el10_2 | 1:24.19.0-1.el10_2 |
| AlmaLinux:10 | nodejs24-full-i18n | before 1:24.19.0-1.el10_2 | 1:24.19.0-1.el10_2 |
| AlmaLinux:10 | nodejs24-libs | before 1:24.19.0-1.el10_2 | 1:24.19.0-1.el10_2 |
| AlmaLinux:10 | nodejs24-npm | before 1:11.17.0-1.24.19.0.1.el10_2 | 1:11.17.0-1.24.19.0.1.el10_2 |
| AlmaLinux:8 | nodejs | before 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a | 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a |
| AlmaLinux:8 | nodejs | before 1:22.23.2-1.module_el8.10.0+4265+75d28086 | 1:22.23.2-1.module_el8.10.0+4265+75d28086 |
| AlmaLinux:8 | nodejs-devel | before 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a | 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a |
| AlmaLinux:8 | nodejs-devel | before 1:22.23.2-1.module_el8.10.0+4265+75d28086 | 1:22.23.2-1.module_el8.10.0+4265+75d28086 |
| AlmaLinux:8 | nodejs-docs | before 1:22.23.2-1.module_el8.10.0+4265+75d28086 | 1:22.23.2-1.module_el8.10.0+4265+75d28086 |
| AlmaLinux:8 | nodejs-docs | before 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a | 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a |
| AlmaLinux:8 | nodejs-full-i18n | before 1:22.23.2-1.module_el8.10.0+4265+75d28086 | 1:22.23.2-1.module_el8.10.0+4265+75d28086 |
| AlmaLinux:8 | nodejs-full-i18n | before 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a | 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a |
| AlmaLinux:8 | nodejs-libs | before 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a | 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a |
| AlmaLinux:8 | nodejs-libs | before 1:22.23.2-1.module_el8.10.0+4265+75d28086 | 1:22.23.2-1.module_el8.10.0+4265+75d28086 |
| AlmaLinux:8 | nodejs-nodemon | before 3.1.14-2.module_el8.10.0+4250+09238ed4 | 3.1.14-2.module_el8.10.0+4250+09238ed4 |
| AlmaLinux:8 | nodejs-nodemon | before 3.1.14-2.module_el8.10.0+4252+aedd4c30 | 3.1.14-2.module_el8.10.0+4252+aedd4c30 |
+96
Same product
nodejs: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-27983An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2…57Plan
- CVE-2025-27210An incomplete fix has been identified for CVE-2025-23084 in Node.js, specifically affecting Windows device names like CON, PRN, and AUX.34Monitor
- CVE-2026-123872Node.js is vulnerable to a client certificate authentication bypass via TLS 1.2 renegotiation servername change32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-56846Aug 4, 2026 · A flaw in Node.js HTTP/2 handling can cause HTTP/2 retained header blocks evade maxSessionMemory and enable remote memory exhaustion.30Monitor
- ← EarlierCVE-2026-58041Aug 4, 2026 · A flaw in Node.js node:sqlite allows a stale StatementSyncIterator created through DatabaseSync#createTagStore() to continue executing a…21Monitor
- Later →CVE-2026-58044Aug 4, 2026 · A flaw in Node.js HTTP client can cause a request desynchronization for Node.js-based forwarding proxies that rebuild outbound headers from…14Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:nodejs | 1:22.23.2-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs-devel | 1:22.23.2-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs-docs | 1:22.23.2-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs-full-i18n | 1:22.23.2-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs-libs | 1:22.23.2-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs-npm | 1:10.9.8-1.22.23.2.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24 | 1:24.19.0-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24-devel | 1:24.19.0-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24-docs | 1:24.19.0-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24-full-i18n | 1:24.19.0-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24-libs | 1:24.19.0-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24-npm | 1:11.17.0-1.24.19.0.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| alpine:nodejs | 22.23.2-r0 · Alpine:v3.21 | Package registry (OSV) |
| alpine:nodejs-current | 26.5.1-r0 · Alpine:v3.24 | Package registry (OSV) |
| debian:nodejs | 18.20.4+dfsg-1~deb12u3 · Debian:12 | Package registry (OSV) |
| debian:nodejs | 20.19.2+dfsg-1+deb13u3 · Debian:13 | Package registry (OSV) |
| opensuse:nodejs22 | 22.23.2-160000.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:nodejs24 | 24.18.1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:nodejs26 | 26.5.1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:nodejs22 | 0:22.23.2-2.3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs22 | 1:22.23.2-2.3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs22-bin | 0:22.23.2-2.3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs22-bin | 1:22.23.2-2.3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs22-devel | 0:22.23.2-2.3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs22-devel | 1:22.23.2-2.3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs22-docs | 0:22.23.2-2.3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs22-docs | 1:22.23.2-2.3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs22-full-i18n | 0:22.23.2-2.3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs22-full-i18n | 1:22.23.2-2.3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs22-libs | 0:22.23.2-2.3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
+17
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2026-10-23 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+80 d
- TodayNov 16, 2026+104 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-568460 days apartA flaw in Node.js HTTP/2 handling can cause HTTP/2 retained header blocks evade maxSessionMemory and enable remote memory exhaustion.30Monitor
- CVE-2026-12386599 days apartNode.js is vulnerable to an HTTP/2 memory and file-descriptor leak via a protocol error during session shutdown30Monitor
- CVE-2026-580450 days apartA flaw in Node.js allows a spoofed `TypedArray` `byteLength` to trigger a reachable assertion in the synchronous `node:zlib` APIs, causing…24Monitor
- CVE-2026-12386899 days apartNode.js is vulnerable to an HTTP/2 memory exhaustion denial of service via unaccounted inbound DATA on an undrained stream23Monitor
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0731 · Aug 4, 2026(Node.js Güvenlik Bildirimi )
Not on record for this CVE: patch commit or PR link · researcher credit.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (2)
- Exploit maturitynone → poc
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.