Node
nodejs- Software type
- —
- Catalog vulnerabilities
- 120
Severity across 103 analyzed records
Verify to analyze this security profile
A short verification protects source data and prevents automated AI requests.
en
Severity across 103 analyzed records
A short verification protects source data and prevents automated AI requests.
The GCVE catalog currently lists 120 vulnerability records affecting Node.
Among the 103 records analyzed by CyStack, 36 are High or Critical and 0 appear in the CISA KEV catalog.
Compare the version you run with each vulnerability and the provider guidance below. The data only includes records analyzed so far.
| CVE | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-48932CVE-2026-48932 | Exploitation statusNot known exploited | FixYes | Published09/01/2026 | SeverityLow |
CVE-2026-56848CVE-2026-56848 | Exploitation statusNot known exploited | FixYes | Published08/04/2026 | SeverityHigh |
CVE-2026-58042CVE-2026-58042 | Exploitation statusNot known exploited | FixYes | Published08/04/2026 | SeverityMedium |
CVE-2026-56846CVE-2026-56846 | Exploitation statusNot known exploited | FixYes | Published08/04/2026 | SeverityHigh |
CVE-2026-58044CVE-2026-58044 | Exploitation statusNot known exploited | FixYes | Published08/04/2026 | SeverityLow |
CVE-2026-58045CVE-2026-58045 | Exploitation statusNot known exploited | FixYes | Published08/04/2026 | SeverityMedium |
CVE-2026-58041CVE-2026-58041 | Exploitation statusNot known exploited | FixYes | Published08/04/2026 | SeverityMedium |
CVE-2026-58039CVE-2026-58039 | Exploitation statusNot known exploited | FixYes | Published07/31/2026 | SeverityLow |
CVE-2026-56847CVE-2026-56847 | Exploitation statusNot known exploited | FixYes | Published07/30/2026 | SeverityLow |
CVE-2026-58043CVE-2026-58043 | Exploitation statusNot known exploited | FixYes | Published07/30/2026 | SeverityHigh |
CVE-2026-56850CVE-2026-56850 | Exploitation statusNot known exploited | FixYes | Published07/30/2026 | SeverityMedium |
CVE-2026-58040CVE-2026-58040 | Exploitation statusNot known exploited | FixYes | Published07/30/2026 | SeverityMedium |
CVE-2026-48930CVE-2026-48930 | Exploitation statusNot known exploited | FixYes | Published06/26/2026 | SeverityMedium |
CVE-2026-48928CVE-2026-48928 | Exploitation statusNot known exploited | FixYes | Published06/26/2026 | SeverityMedium |
CVE-2026-48934CVE-2026-48934 | Exploitation statusNot known exploited | FixYes | Published06/26/2026 | SeverityMedium |
CVE-2026-48936CVE-2026-48936 | Exploitation statusNot known exploited | FixYes | Published06/26/2026 | SeverityLow |
CVE-2026-48618CVE-2026-48618 | Exploitation statusNot known exploited | FixYes | Published06/26/2026 | SeverityHigh |
CVE-2026-48933CVE-2026-48933 | Exploitation statusNot known exploited | FixYes | Published06/26/2026 | SeverityHigh |
CVE-2026-48935CVE-2026-48935 | Exploitation statusNot known exploited | FixYes | Published06/26/2026 | SeverityLow |
CVE-2026-48619CVE-2026-48619 | Exploitation statusNot known exploited | FixYes | Published06/26/2026 | SeverityMedium |
CVE-2026-48615CVE-2026-48615 | Exploitation statusNot known exploited | FixYes | Published06/26/2026 | SeverityMedium |
CVE-2026-48931CVE-2026-48931 | Exploitation statusNot known exploited | FixYes | Published06/22/2026 | SeverityLow |
CVE-2026-48937CVE-2026-48937 | Exploitation statusNot known exploited | FixYes | Published06/18/2026 | SeverityMedium |
CVE-2026-48617CVE-2026-48617 | Exploitation statusNot known exploited | FixYes | Published06/18/2026 | SeverityLow |
CVE-2026-21710CVE-2026-21710 | Exploitation statusNot known exploited | FixYes | Published03/30/2026 | SeverityHigh |
CVE-2026-21716CVE-2026-21716 | Exploitation statusNot known exploited | FixYes | Published03/30/2026 | SeverityLow |
CVE-2026-21711CVE-2026-21711 | Exploitation statusNot known exploited | FixYes | Published03/30/2026 | SeverityMedium |
CVE-2026-21715CVE-2026-21715 | Exploitation statusNot known exploited | FixYes | Published03/30/2026 | SeverityLow |
CVE-2026-21717CVE-2026-21717 | Exploitation statusNot known exploited | FixYes | Published03/30/2026 | SeverityMedium |
CVE-2026-21713CVE-2026-21713 | Exploitation statusNot known exploited | FixYes | Published03/30/2026 | SeverityMedium |
CVE-2026-21714CVE-2026-21714 | Exploitation statusNot known exploited | FixYes | Published03/30/2026 | SeverityMedium |
CVE-2026-21712CVE-2026-21712 | Exploitation statusNot known exploited | FixYes | Published03/30/2026 | SeverityMedium |
CVE-2026-21636CVE-2026-21636 | Exploitation statusNot known exploited | FixYes | Published01/20/2026 | SeverityMedium |
CVE-2025-59466CVE-2025-59466 | Exploitation statusNot known exploited | FixYes | Published01/20/2026 | SeverityMedium |
CVE-2025-55132CVE-2025-55132 | Exploitation statusNot known exploited | FixYes | Published01/20/2026 | SeverityLow |
CVE-2025-59464CVE-2025-59464 | Exploitation statusNot known exploited | FixYes | Published01/20/2026 | SeverityMedium |
CVE-2025-55131CVE-2025-55131 | Exploitation statusNot known exploited | FixYes | Published01/20/2026 | SeverityHigh |
CVE-2025-55130CVE-2025-55130 | Exploitation statusNot known exploited | FixYes | Published01/20/2026 | SeverityHigh |
CVE-2026-21637CVE-2026-21637 | Exploitation statusNot known exploited | FixYes | Published01/20/2026 | SeverityMedium |
CVE-2025-59465CVE-2025-59465 | Exploitation statusNot known exploited | FixYes | Published01/20/2026 | SeverityHigh |
CVE-2025-27210CVE-2025-27210 | Exploitation statusNot known exploited | FixYes | Published07/18/2025 | SeverityHigh |
CVE-2025-27209CVE-2025-27209 | Exploitation statusNot known exploited | FixYes | Published07/18/2025 | SeverityHigh |
CVE-2025-23165CVE-2025-23165 | Exploitation statusPublic exploit | FixYes | Published05/19/2025 | SeverityLow |
CVE-2025-23166CVE-2025-23166 | Exploitation statusNot known exploited | FixYes | Published05/19/2025 | SeverityHigh |
CVE-2025-23167CVE-2025-23167 | Exploitation statusNot known exploited | FixYes | Published05/19/2025 | SeverityMedium |
CVE-2025-23085CVE-2025-23085 | Exploitation statusNot known exploited | FixYes | Published02/07/2025 | SeverityMedium |
CVE-2025-23084CVE-2025-23084 | Exploitation statusNot known exploited | FixYes | Published01/28/2025 | SeverityMedium |
CVE-2025-23083CVE-2025-23083 | Exploitation statusNot known exploited | FixYes | Published01/22/2025 | SeverityHigh |
CVE-2024-27980CVE-2024-27980 | Exploitation statusNot known exploited | FixYes | Published01/09/2025 | SeverityHigh |
CVE-2024-37372CVE-2024-37372 | Exploitation statusNot known exploited | FixYes | Published01/09/2025 | SeverityLow |
CVE-2023-46809CVE-2023-46809 | Exploitation statusNot known exploited | FixYes | Published09/07/2024 | SeverityHigh |
CVE-2024-36138CVE-2024-36138 | Exploitation statusNot known exploited | FixYes | Published09/07/2024 | SeverityHigh |
CVE-2023-39333CVE-2023-39333 | Exploitation statusNot known exploited | FixYes | Published09/07/2024 | SeverityMedium |
CVE-2024-36137CVE-2024-36137 | Exploitation statusNot known exploited | FixYes | Published09/07/2024 | SeverityLow |
CVE-2023-30582CVE-2023-30582 | Exploitation statusNot known exploited | FixYes | Published09/07/2024 | SeverityMedium |
CVE-2023-30587CVE-2023-30587 | Exploitation statusNot known exploited | FixYes | Published09/07/2024 | SeverityHigh |
CVE-2023-30583CVE-2023-30583 | Exploitation statusNot known exploited | FixYes | Published09/07/2024 | SeverityHigh |
CVE-2023-30584CVE-2023-30584 | Exploitation statusNot known exploited | FixYes | Published09/07/2024 | SeverityHigh |
CVE-2024-22018CVE-2024-22018 | Exploitation statusNot known exploited | FixYes | Published07/10/2024 | SeverityLow |
CVE-2024-22020CVE-2024-22020 | Exploitation statusNot known exploited | FixYes | Published07/09/2024 | SeverityMedium |
CVE-2024-27982CVE-2024-27982 | Exploitation statusNot known exploited | FixYes | Published05/07/2024 | SeverityMedium |
CVE-2024-27983CVE-2024-27983 | Exploitation statusNot known exploited | FixYes | Published04/09/2024 | SeverityHigh |
CVE-2024-22025CVE-2024-22025 | Exploitation statusNot known exploited | FixYes | Published03/19/2024 | SeverityMedium |
CVE-2024-22017CVE-2024-22017 | Exploitation statusNot known exploited | FixYes | Published03/19/2024 | SeverityHigh |
CVE-2024-21896CVE-2024-21896 | Exploitation statusNot known exploited | FixYes | Published02/20/2024 | SeverityHigh |
CVE-2024-21890CVE-2024-21890 | Exploitation statusNot known exploited | FixYes | Published02/20/2024 | SeverityMedium |
CVE-2024-21891CVE-2024-21891 | Exploitation statusNot known exploited | FixYes | Published02/20/2024 | SeverityHigh |
CVE-2024-22019CVE-2024-22019 | Exploitation statusNot known exploited | FixYes | Published02/20/2024 | SeverityHigh |
CVE-2024-21892CVE-2024-21892 | Exploitation statusNot known exploited | FixYes | Published02/20/2024 | SeverityHigh |
CVE-2023-30590CVE-2023-30590 | Exploitation statusNot confirmed | FixYes | Published11/28/2023 | SeverityUnknown |
CVE-2023-30588CVE-2023-30588 | Exploitation statusNot confirmed | FixYes | Published11/28/2023 | SeverityUnknown |
CVE-2023-30585CVE-2023-30585 | Exploitation statusNot confirmed | FixYes | Published11/28/2023 | SeverityUnknown |
CVE-2023-30581CVE-2023-30581 | Exploitation statusNot known exploited | FixYes | Published11/22/2023 | SeverityHigh |
CVE-2023-39331CVE-2023-39331 | Exploitation statusNot known exploited | FixYes | Published10/18/2023 | SeverityHigh |
CVE-2023-38552CVE-2023-38552 | Exploitation statusNot known exploited | FixYes | Published10/18/2023 | SeverityUnknown |
CVE-2023-39332CVE-2023-39332 | Exploitation statusNot known exploited | FixYes | Published10/18/2023 | SeverityUnknown |
CVE-2023-32558CVE-2023-32558 | Exploitation statusNot confirmed | FixYes | Published09/12/2023 | SeverityUnknown |
CVE-2023-32005CVE-2023-32005 | Exploitation statusPublic exploit | FixYes | Published09/12/2023 | SeverityMedium |
CVE-2023-32559CVE-2023-32559 | Exploitation statusNot known exploited | FixYes | Published08/24/2023 | SeverityHigh |
CVE-2023-32002CVE-2023-32002 | Exploitation statusNot known exploited | FixYes | Published08/21/2023 | SeverityCritical |
CVE-2023-32003CVE-2023-32003 | Exploitation statusNot known exploited | FixYes | Published08/15/2023 | SeverityMedium |
CVE-2023-32004CVE-2023-32004 | Exploitation statusNot known exploited | FixYes | Published08/15/2023 | SeverityHigh |
CVE-2023-32006CVE-2023-32006 | Exploitation statusNot known exploited | FixYes | Published08/15/2023 | SeverityHigh |
CVE-2023-30586CVE-2023-30586 | Exploitation statusNot known exploited | FixYes | Published06/30/2023 | SeverityHigh |
CVE-2023-30589CVE-2023-30589 | Exploitation statusNot confirmed | FixYes | Published06/30/2023 | SeverityUnknown |
CVE-2023-23919CVE-2023-23919 | Exploitation statusPublic exploit | FixYes | Published02/23/2023 | SeverityHigh |
CVE-2023-23920CVE-2023-23920 | Exploitation statusNot known exploited | FixYes | Published02/23/2023 | SeverityMedium |
CVE-2023-23918CVE-2023-23918 | Exploitation statusNot known exploited | FixYes | Published02/23/2023 | SeverityHigh |
CVE-2022-35255CVE-2022-35255 | Exploitation statusNot known exploited | FixYes | Published12/05/2022 | SeverityCritical |
CVE-2022-35256CVE-2022-35256 | Exploitation statusPublic exploit | FixYes | Published12/05/2022 | SeverityMedium |
CVE-2022-43548CVE-2022-43548 | Exploitation statusNot known exploited | FixYes | Published12/05/2022 | SeverityHigh |
CVE-2022-32223CVE-2022-32223 | Exploitation statusNot confirmed | FixYes | Published07/14/2022 | SeverityUnknown |
CVE-2022-32214CVE-2022-32214 | Exploitation statusNot confirmed | FixYes | Published07/14/2022 | SeverityUnknown |
CVE-2022-32212CVE-2022-32212 | Exploitation statusNot confirmed | FixYes | Published07/14/2022 | SeverityUnknown |
CVE-2022-32213CVE-2022-32213 | Exploitation statusNot confirmed | FixYes | Published07/14/2022 | SeverityUnknown |
CVE-2022-32215CVE-2022-32215 | Exploitation statusNot confirmed | FixYes | Published07/14/2022 | SeverityUnknown |
CVE-2022-32222CVE-2022-32222 | Exploitation statusNot confirmed | FixYes | Published07/14/2022 | SeverityUnknown |
CVE-2021-44533CVE-2021-44533 | Exploitation statusNot confirmed | FixYes | Published02/24/2022 | SeverityUnknown |
CVE-2021-44532CVE-2021-44532 | Exploitation statusNot confirmed | FixYes | Published02/24/2022 | SeverityUnknown |
CVE-2021-44531CVE-2021-44531 | Exploitation statusNot confirmed | FixYes | Published02/24/2022 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan