CVE-2026-58040: An incomplete fix has been identified in Node.js: HTTPS Agent TLS session reuse skips hostname verification across identity policies (incomp
Noroxi assessment
Priority: Monitor (action score 25/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.27% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: azl3 nodejs 24.17.0-1 on Azure Linux 3.0 24.18.1-1.
Low priority for now. Upgrade to azl3 nodejs 24.17.0-1 on Azure Linux 3.0 24.18.1-1 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
An incomplete fix has been identified in Node.js: HTTPS Agent TLS session reuse skips hostname verification across identity policies (incomplete fix of CVE-2026-48934). This vulnerability affects Node.js **22.x**, **24.x**, and **26.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:48273
- RHSA-2026:48305
- RHSA-2026:48537
- RHSA-2026:61376
- RHSA-2026:61377
- RHSA-2026:61383
- RHSA-2026:61386
- RHSA-2026:62219
- RHSA-2026:62416
- RHSA-2026:62583
- Published
- Jul 30, 2026
- Updated
- Oct 23, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- CWE-297
Report tools
Action score
25
Monitor
Low priority for now.
- CVSS
- 25 / 40 · 6.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · hackerone
- 6.3
- 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)
Check your site's encryption
This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.
Run the SSL checkVersions 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.1 and later · up to and including 22.23.1affected · semver
- 24.18.0 and later · up to and including 24.18.0affected · semver
- 26.5.0 and later · up to and including 26.5.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: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:22.23.2-1.module_el8.10.0+4265+75d28086 | 1:22.23.2-1.module_el8.10.0+4265+75d28086 |
| 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-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-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-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: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-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-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-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 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-2025-27209Jul 18, 2025 · The V8 release used in Node.js v24.0.0 has changed how string hashes are computed using rapidhash.30Monitor
- ← EarlierCVE-2025-55131Jan 20, 2026 · A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted, when using the `vm` module wit29Monitor
- Later →CVE-2026-58039Jul 31, 2026 · A flaw in Node.js Permission Model enforcement allows process.report writes (and overwrites) files outside --allow-fs-write paths.13Monitor
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.17.0-1 on Azure Linux 3.0 | 24.18.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| 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 | 24.19.0+dfsg+~cs24.13.3-1 · Debian:14 | 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-bin | 0: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-docs | 0:22.23.2-2.3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs24 | 0:24.18.1-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs24-bin | 0:24.18.1-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs26 | 0:26.5.1-1.5.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs26-bin | 0:26.5.1-1.5.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs26-devel | 0:26.5.1-1.5.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs26-docs | 0:26.5.1-1.5.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
+6
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+85 d
- TodayNov 8, 2026+102 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.
No nightly-computed relations.
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.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-297 · Improper Validation of Certificate with Host MismatchCVSS vector
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- 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.