This page was not yet optimized for use on mobile devices.
CVE-2026-34226
Data
| Vulnerability ID | CVE-2026-34226 |
|---|---|
| Published on | 27.03.2026 22:16 |
| Severity | HIGH |
Vulnerable configurations
-
cpe:2.3:a:capricorn86:happy_dom:0.0.1:*:*:*:*:node.js:*:*,
cpe:2.3:a:capricorn86:happy_dom:0.0.2:*:*:*:*:node.js:*:*,
cpe:2.3:a:capricorn86:happy_dom:0.0.3:*:*:*:*:node.js:*:*,
cpe:2.3:a:capricorn86:happy_dom:0.1.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:capricorn86:happy_dom:0.2.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:capricorn86:happy_dom:0.2.1:*:*:*:*:node.js:*:*,
cpe:2.3:a:capricorn86:happy_dom:0.2.2:*:*:*:*:node.js:*:*,
cpe:2.3:a:capricorn86:happy_dom:0.2.3:*:*:*:*:node.js:*:*,
cpe:2.3:a:capricorn86:happy_dom:0.2.4:*:*:*:*:node.js:*:*,
cpe:2.3:a:capricorn86:happy_dom:0.2.5:*:*:*:*:node.js:*:*,
…
Vulnerable certificates
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.