← Search results
CVE-LINKED INVENTORY16 SECURITY RECORDS
The Node.js Project
Node.js
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 node.js, 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-2018-12123 | 28 Nov 2018 | All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0 | 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-2018-12122 | 28 Nov 2018 | All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0 | 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-2018-12121 | 28 Nov 2018 | All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0 | 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-2018-12120 | 28 Nov 2018 | All versions prior to Node.js 6.15.0 | 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-2018-12116 | 28 Nov 2018 | All versions prior to Node.js 6.15.0 and 8.14.0 | 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-2018-7166 | 21 Aug 2018 | All versions of Node.js 10 prior to 10.9.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-12115 | 21 Aug 2018 | All versions of Node.js prior to 6.14.4, 8.11.4 and 10.9.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-7167 | 13 Jun 2018 | 6.x+; 8.x+; 9.x+; 10.x+ | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-7164 | 13 Jun 2018 | 9.7.X+; 10.x+ | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-7162 | 13 Jun 2018 | 9.x+; 10.x+ | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-7161 | 13 Jun 2018 | 8.x+; 9.x+; 10.x+ | 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-2018-7160 | 17 May 2018 | ^6.0.0 || ^8.0.0 || ^9.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-7159 | 17 May 2018 | 4.x; 6.x; 8.x; 9.x | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-7158 | 17 May 2018 | 4.x | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-15897 | 11 Dec 2017 | 8.0 and higher; 9.0 and higher | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-15896 | 11 Dec 2017 | 4.0.0 and higher; 6.0.0 and higher; 8.0.0 and higher; 9.0.0 and higher | 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.