capricorn86
happy-dom
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at happy-dom, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-34226 | 27 Mar 2026 | < 20.8.9 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-33943 | 27 Mar 2026 | >= 15.10.0, < 20.8.8 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2025-62410 | 15 Oct 2025 | happy-dom: < 20.0.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-61927 | 10 Oct 2025 | happy-dom: < 20.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-51757 | 6 Nov 2024 | < 15.10.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.