A flaw in Node.js WebCrypto implementation can crash the process if the input of `subtle.encrypt()` is a multiple of 2GiB.
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.7% (FIRST EPSS); higher than 89.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: nodejs (AlmaLinux:10) 1:22.23.1-2.el10_2; nodejs-devel (AlmaLinux:10) 1:22.23.1-2.el10_2; nodejs-docs (AlmaLinux:10) 1:22.23.1-2.el10_2.
Low priority for now. Upgrade to nodejs (AlmaLinux:10) 1:22.23.1-2.el10_2; nodejs-devel (AlmaLinux:10) 1:22.23.1-2.el10_2; nodejs-docs (AlmaLinux:10) 1:22.23.1-2.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 WebCrypto implementation can crash the process if the input of `subtle.encrypt()` is a multiple of 2GiB. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
- ALSA-2026:35841
- ALSA-2026:35842
- ALSA-2026:35891
- ALSA-2026:35892
- ALSA-2026:39868
- ALSA-2026:41947
- openSUSE-SU-2026:11121-1
- openSUSE-SU-2026:21058-1
- openSUSE-SU-2026:21236-1
- RHSA-2026:28727
- RHSA-2026:29012
- RHSA-2026:30172
- RHSA-2026:35841
- RHSA-2026:35842
- RHSA-2026:35891
- RHSA-2026:35892
- RHSA-2026:39246
- RHSA-2026:39868
- RHSA-2026:41947
- RHSA-2026:52399
- Published
- Jun 25, 2026
- Updated
- Aug 10, 2026
- EPSS
- 3.7% · 89th percentile
- CWE
- CWE-190
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · hackerone
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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
- No public exploit code on record
- 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.
| Vendor | Product | CPE |
|---|---|---|
| nodejs | node.js | cpe:2.3:a:nodejs:node.js |
Using node.js? Add it to your stack and be the first to know about CVEs like this one. (Node.js)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nodejs node.js22.22.3
- nodejs node.js24.16.0
- nodejs node.js26.3.0
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.22.3 and later · up to and including 22.22.3affected · semver
- 24.16.0 and later · up to and including 24.16.0affected · semver
- 26.3.0 and later · up to and including 26.3.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.1-2.el10_2 | 1:22.23.1-2.el10_2 |
| AlmaLinux:10 | nodejs-devel | before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
| AlmaLinux:10 | nodejs-docs | before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
| AlmaLinux:10 | nodejs-full-i18n | before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
| AlmaLinux:10 | nodejs-libs | before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
| AlmaLinux:10 | nodejs-npm | before 1:10.9.8-1.22.23.1.2.el10_2 | 1:10.9.8-1.22.23.1.2.el10_2 |
| AlmaLinux:10 | nodejs24 | before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
| AlmaLinux:10 | nodejs24-devel | before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
| AlmaLinux:10 | nodejs24-docs | before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
| AlmaLinux:10 | nodejs24-full-i18n | before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
| AlmaLinux:10 | nodejs24-libs | before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
| AlmaLinux:10 | nodejs24-npm | before 1:11.16.0-1.24.18.0.1.el10_2 | 1:11.16.0-1.24.18.0.1.el10_2 |
| AlmaLinux:8 | nodejs | before 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 | 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 |
| AlmaLinux:8 | nodejs | before 1:24.18.0-1.module_el8.10.0+4228+2938bc94 | 1:24.18.0-1.module_el8.10.0+4228+2938bc94 |
| AlmaLinux:8 | nodejs-devel | before 1:24.18.0-1.module_el8.10.0+4228+2938bc94 | 1:24.18.0-1.module_el8.10.0+4228+2938bc94 |
| AlmaLinux:8 | nodejs-devel | before 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 | 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 |
| AlmaLinux:8 | nodejs-docs | before 1:24.18.0-1.module_el8.10.0+4228+2938bc94 | 1:24.18.0-1.module_el8.10.0+4228+2938bc94 |
| AlmaLinux:8 | nodejs-docs | before 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 | 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 |
| AlmaLinux:8 | nodejs-full-i18n | before 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 | 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 |
| AlmaLinux:8 | nodejs-full-i18n | before 1:24.18.0-1.module_el8.10.0+4228+2938bc94 | 1:24.18.0-1.module_el8.10.0+4228+2938bc94 |
| AlmaLinux:8 | nodejs-libs | before 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 | 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 |
| AlmaLinux:8 | nodejs-libs | before 1:24.18.0-1.module_el8.10.0+4228+2938bc94 | 1:24.18.0-1.module_el8.10.0+4228+2938bc94 |
| AlmaLinux:8 | nodejs-nodemon | before 3.0.1-1.module_el8.10.0+3956+47c9ee9f | 3.0.1-1.module_el8.10.0+3956+47c9ee9f |
| AlmaLinux:8 | nodejs-nodemon | before 3.0.3-1.module_el8.10.0+4061+f8ceeab9 | 3.0.3-1.module_el8.10.0+4061+f8ceeab9 |
+96
Same product
nodejs: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-15605HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed56Plan
- CVE-2021-22883Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an 53Plan
- CVE-2021-22930Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory c50Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-48928Jun 25, 2026 · A inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups.21Monitor
- ← EarlierCVE-2026-48930Jun 25, 2026 · A flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation i39Monitor
- Later →CVE-2026-48934Jun 25, 2026 · A flaw in Node.js TLS host verification can cause an attacker to bypass certification validation.17Monitor
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.1-2.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs-devel | 1:22.23.1-2.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs-docs | 1:22.23.1-2.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs-full-i18n | 1:22.23.1-2.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs-libs | 1:22.23.1-2.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs-npm | 1:10.9.8-1.22.23.1.2.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24 | 1:24.18.0-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24-devel | 1:24.18.0-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24-docs | 1:24.18.0-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24-full-i18n | 1:24.18.0-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24-libs | 1:24.18.0-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24-npm | 1:11.16.0-1.24.18.0.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| alpine:nodejs | 22.23.0-r0 · Alpine:v3.21 | 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.0-160000.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:nodejs24 | 24.17.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:nodejs22 | 0:22.23.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs22-bin | 0:22.23.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs22-devel | 0:22.23.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs22-docs | 0:22.23.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs22-full-i18n | 0:22.23.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs22-libs | 0:22.23.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs22-npm | 0:10.9.8-1.22.23.1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs22-npm-bin | 0:22.23.1-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs24 | 0:24.18.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs24-bin | 0:24.18.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs24-debuginfo | 1:24.18.0-1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:nodejs24-debugsource | 1:24.18.0-1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:nodejs24-devel | 0:24.18.0-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
+15
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
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.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (16 more)Show less
- access.redhat.com/errata/RHSA-2026:28727
- access.redhat.com/errata/RHSA-2026:29012
- access.redhat.com/errata/RHSA-2026:30172
- access.redhat.com/errata/RHSA-2026:35841
- access.redhat.com/errata/RHSA-2026:35842
- access.redhat.com/errata/RHSA-2026:35891
- access.redhat.com/errata/RHSA-2026:35892
- access.redhat.com/errata/RHSA-2026:39246
- access.redhat.com/errata/RHSA-2026:39868
- access.redhat.com/errata/RHSA-2026:41947
- access.redhat.com/errata/RHSA-2026:52399
- access.redhat.com/errata/RHSA-2026:7378
- access.redhat.com/errata/RHSA-2026:9455
- access.redhat.com/security/cve/CVE-2026-48933
- bugzilla.redhat.com/show_bug.cgi?id=2493331
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-48933.json
Vendor advisories and official records. Exploit/PoC links are deliberately left out.