CVE-2026-105482: A flaw in Node.js DNS resolution allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*() functions and dns.rev
Noroxi assessment
Priority: Monitor (action score 29/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.46% (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: azl3 nodejs 24.21.0-1 on Azure Linux 3.0 24.22.1-0.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to azl3 nodejs 24.21.0-1 on Azure Linux 3.0 24.22.1-0 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 DNS resolution allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*() functions and dns.reverse(). This is an incomplete fix of CVE-2026-48930, which only covered dns.lookup() and the net/tls host options. Because the name is passed to c-ares as a C string, resolving attacker.example\0.trusted.example queries attacker.example and returns its records without any error. Applications that validate a hostname, for example against a domain allowlist, and then resolve it with dns.resolve*() can act on records for a different name than the one they validated. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
- Published
- Oct 23, 2026
- Updated
- Nov 2, 2026
- EPSS
- 0.4% · 40th percentile
- CWE
- CWE-284
Report tools
Action score
29
Monitor
Low priority for now.
- CVSS
- 29 / 40 · 7.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · hackerone
- 7.4
- 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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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
- 22.23.3 and later · up to and including 22.23.3affected · semver
- 24.22.0 and later · up to and including 24.22.0affected · semver
- 26.12.0 and later · up to and including 26.12.0affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | nodejs | before 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 | 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 |
| AlmaLinux:8 | nodejs-devel | before 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 | 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 |
| AlmaLinux:8 | nodejs-docs | before 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 | 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 |
| AlmaLinux:8 | nodejs-full-i18n | before 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 | 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 |
| AlmaLinux:8 | nodejs-libs | before 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 | 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 |
| 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-packaging | before 2021.06-6.module_el8.10.0+4086+70facd4a | 2021.06-6.module_el8.10.0+4086+70facd4a |
| AlmaLinux:8 | nodejs-packaging-bundler | before 2021.06-6.module_el8.10.0+4086+70facd4a | 2021.06-6.module_el8.10.0+4086+70facd4a |
| AlmaLinux:8 | npm | before 1:11.19.1-1.24.22.1.1.module_el8.10.0+4331+0683c9c1 | 1:11.19.1-1.24.22.1.1.module_el8.10.0+4331+0683c9c1 |
| AlmaLinux:8 | v8-13.6-devel | before 3:13.6.233.17-1.24.22.1.1.module_el8.10.0+4331+0683c9c1 | 3:13.6.233.17-1.24.22.1.1.module_el8.10.0+4331+0683c9c1 |
| AlmaLinux:9 | nodejs | before 1:24.22.1-3.module_el9.8.0+333+788f3075 | 1:24.22.1-3.module_el9.8.0+333+788f3075 |
| AlmaLinux:9 | nodejs-devel | before 1:24.22.1-3.module_el9.8.0+333+788f3075 | 1:24.22.1-3.module_el9.8.0+333+788f3075 |
| AlmaLinux:9 | nodejs-docs | before 1:24.22.1-3.module_el9.8.0+333+788f3075 | 1:24.22.1-3.module_el9.8.0+333+788f3075 |
| AlmaLinux:9 | nodejs-full-i18n | before 1:24.22.1-3.module_el9.8.0+333+788f3075 | 1:24.22.1-3.module_el9.8.0+333+788f3075 |
| AlmaLinux:9 | nodejs-libs | before 1:24.22.1-3.module_el9.8.0+333+788f3075 | 1:24.22.1-3.module_el9.8.0+333+788f3075 |
| AlmaLinux:9 | nodejs-nodemon | before 3.1.14-3.module_el9.8.0+292+f4eaf8b2 | 3.1.14-3.module_el9.8.0+292+f4eaf8b2 |
| AlmaLinux:9 | nodejs-packaging | before 2021.06-6.module_el9.7.0+209+ecf6523e | 2021.06-6.module_el9.7.0+209+ecf6523e |
| AlmaLinux:9 | nodejs-packaging-bundler | before 2021.06-6.module_el9.7.0+209+ecf6523e | 2021.06-6.module_el9.7.0+209+ecf6523e |
| AlmaLinux:9 | npm | before 1:11.19.1-1.24.22.1.3.module_el9.8.0+333+788f3075 | 1:11.19.1-1.24.22.1.3.module_el9.8.0+333+788f3075 |
| AlmaLinux:9 | v8-13.6-devel | before 3:13.6.233.17-1.24.22.1.3.module_el9.8.0+333+788f3075 | 3:13.6.233.17-1.24.22.1.3.module_el9.8.0+333+788f3075 |
| Alpine:v3.21 | nodejs | before 22.23.4-r0 | 22.23.4-r0 |
| Alpine:v3.23 | nodejs | before 24.22.1-r0 | 24.22.1-r0 |
| Alpine:v3.24 | nodejs-current | before 26.12.1-r0 | 26.12.1-r0 |
| Debian:12 | nodejs | from 0 | — |
+16
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 f58Plan
- 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-2024-27980Due to the improper handling of batch files in child_process.spawn / child_process.spawnSync, a malicious command line argument can inject a32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-48932Aug 31, 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
- ← EarlierCVE-2026-105481Oct 23, 2026 · A flaw in Node.js HTTP Agent connection reuse can cause a client to accept as valid a response that was sent before the client has sent the 26Monitor
- Later →CVE-2026-105483Oct 23, 2026 · A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 a29Monitor
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 |
|---|---|---|
| azl3 nodejs 24.21.0-1 on Azure Linux 3.0 | 24.22.1-0 · Release Notes | Microsoft (MSRC) |
| almalinux:nodejs | 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-devel | 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-docs | 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-full-i18n | 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-libs | 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-nodemon | 3.1.14-2.module_el8.10.0+4250+09238ed4 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-packaging | 2021.06-6.module_el8.10.0+4086+70facd4a · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-packaging-bundler | 2021.06-6.module_el8.10.0+4086+70facd4a · AlmaLinux:8 | Package registry (OSV) |
| almalinux:npm | 1:11.19.1-1.24.22.1.1.module_el8.10.0+4331+0683c9c1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:v8-13.6-devel | 3:13.6.233.17-1.24.22.1.1.module_el8.10.0+4331+0683c9c1 · AlmaLinux:8 | Package registry (OSV) |
| alpine:nodejs | 22.23.4-r0 · Alpine:v3.21 | Package registry (OSV) |
| alpine:nodejs-current | 26.12.1-r0 · Alpine:v3.24 | Package registry (OSV) |
| opensuse:nodejs22 | 22.23.4-160000.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:nodejs24 | 24.22.1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| rocky linux:nodejs | 1:24.22.1-3.module+el9.8.0+40401+e24b8c95 · Rocky Linux:9 | Package registry (OSV) |
| rocky linux:nodejs-nodemon | 0:3.1.14-2.module+el8.10.0+40277+b1b3f89e · Rocky Linux:8 | Package registry (OSV) |
| rocky linux:nodejs-packaging | 0:2021.06-6.module+el8.10.0+40048+6d99f608 · Rocky Linux:8 | Package registry (OSV) |
| suse:nodejs22 | 22.23.4-150600.13.27.1 · SUSE:Linux Enterprise Server 15 SP6-LTSS | Package registry (OSV) |
| suse:nodejs24 | 24.22.1-150700.15.21.1 · SUSE:Linux Enterprise Module for Web and Scripting 15 SP7 | Package registry (OSV) |
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 ×3
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:9 | 2026-10-21 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-10-23 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-10-28 |
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.
- First PoC-3 d
- Published
- Fix recorded+1 d
- TodayNov 7, 2026+15 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-1060710 days apartA flaw in Node.js Permission Model filesystem enforcement can grant access to paths that do not match a wildcard `--allow-fs-read` or `--all14Monitor
- CVE-2026-1060730 days apartA flaw in Node.js Permission Model filesystem enforcement leaves `fs.realpathSync()` without the required read permission checks.13Monitor
- CVE-2026-5803984 days apartA flaw in Node.js Permission Model enforcement allows process.report writes (and overwrites) files outside --allow-fs-write paths.13Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
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-1388 · Oct 23, 2026(Node.js Projesi Güvenlik Bildirimi)
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-284 · Improper Access ControlCVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Embedding Scripts within ScriptsCAPEC-19likelihood: High · High
- Malicious Logic InsertionCAPEC-441likelihood: Medium · High
- Modification of Windows Service ConfigurationCAPEC-478likelihood: Low · High
- Malicious Root CertificateCAPEC-479likelihood: Low · Low
- Intent SpoofCAPEC-502
- WebView ExposureCAPEC-503
- Data Injected During ConfigurationCAPEC-536likelihood: Low · High
- Incomplete Data Deletion in a Multi-Tenant EnvironmentCAPEC-546likelihood: Low · Medium
ATT&CK techniques
- RootkitT1014
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Initialization ScriptsT1037
- Taint shared contentT1080
- Server Software Component: Terminal Services DLLT1505.005
- Pre-OS Boot:BootkitT1542.003
- Create or Modify System ProcessT1543
- Create or Modify System Process: Launch AgentT1543.001
- Create or Modify System Process:Windows ServiceT1543.003
- Create or Modify System Process: Launch DaemonT1543.004
- Event Triggered Execution:Change Default File AssociationT1546.001
- Event Triggered Execution:.bash_profile and .bashrcT1546.004
- Event Triggered Execution: Accessibility FeaturesT1546.008
- Event Triggered Execution: Installer PackagesT1546.016
- Boot or Logon Autostart ExecutionT1547
- Boot or Logon Autostart Execution:Kernel Modules and ExtensionsT1547.006
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
- Exploit maturity— → poc
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.