Cryptography

Every one of the 21 is a mark on the map. Named now: 1 to 21, most at risk first.

1. Improper Certificate Validation in Node.js 10, 12, and 13 causes the process to abort when sending a crafted X.509 certificateCVE-2019-15604NodeJS · 20% likely

   CWE-2951 bounty report

2. If the Node.js https API was used incorrectly and "undefined" was in passed for the "rejectUnauthorized" parameter, no error was returned and connections to servers with an expire…CVE-2021-22939NodeJS · 15% likely

   CWE-2951 bounty report

3. Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 converts SANs (Subject Alternative Names) to a string format. It uses this string to check peer certificates against hostname…CVE-2021-44532NodeJS · 10% likely

   CWE-2961 bounty report

4. Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 did not handle multi-value Relative Distinguished Names correctly. Attackers could craft certificate subjects containing a si…CVE-2021-44533NodeJS · 9.4% likely

   CWE-2951 bounty report

5. Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a particular SAN type, can result in bypassing name-constrained intermediates…CVE-2021-44531NodeJS · 8.4% likely

   CWE-2951 bounty report

6. TLS session reuse can lead to host certificate verification bypass in node version < 12.18.0 and < 14.4.0.CVE-2020-8172Nodejs · 6.1% likely

   CWE-2951 bounty report

7. A cryptographic vulnerability exists in Node.js <19.2.0, <18.14.1, <16.19.1, <14.21.3 that in some cases did does not clear the OpenSSL error stack after operations that may set i…CVE-2023-23919NodeJS · CVSS 7.5 · 2.2% likely

   CWE-3102 bounty reports

8. A cryptographic vulnerability exists on Node.js on linux in versions of 18.x prior to 18.40.0 which allowed a default path for openssl.cnf that might be accessible under some circ…CVE-2022-32222NodeJS · 2.2% likely

   CWE-3102 bounty reports

9. A weak randomness in WebCrypto keygen vulnerability exists in Node.js 18 due to a change with EntropySource() in SecretKeyGenTraits::DoKeyGen() in src/crypto/crypto_keygen.cc. The…CVE-2022-35255NodeJS · CVSS 9.1 · 2.1% likely

   CWE-3382 bounty reports

10. When the Node.js policy feature checks the integrity of a resource against a trusted manifest, the application can intercept the operation and return a forged checksum to the node…CVE-2023-38552NodeJS · 1.2% likely

    CWE-3451 bounty report

11. Undici Uses Insufficiently Random ValuesCVE-2025-22150nodejs · CVSS 6.8 · 0.8% likely

    CWE-3301 bounty report

12. A flaw in Node.js TLS hostname verification allows a certificate with only a DNS SAN to authenticate an IP endpoint when the client connects using a non-canonical IPv4 spelling, s…CVE-2026-106072nodejs · CVSS 6.7 · 0.6% likely

    CWE-2951 bounty report

13. `Undici.ProxyAgent` never verifies the remote server's certificate, and always exposes all request & response data to the proxy. This unexpectedly means that proxies can MitM all…CVE-2022-32210Nodejs · 0.5% likely

    CWE-2951 bounty report

14. A flaw in Node.js `crypto` causes the internal entropy caches used by `crypto.randomUUID()`, `crypto.randomUUIDv7()`, and `crypto.randomInt()` to be saved into user-land startup s…CVE-2026-106074nodejs · CVSS 4.8 · 0.3% likely

    CWE-330

15. An incomplete fix has been identified in Node.js: HTTPS Agent TLS session reuse skips hostname verification across identity policies (incomplete fix of CVE-2026-48934). This vulne…CVE-2026-58040nodejs · CVSS 6.3 · 0.3% likely

    CWE-2971 bounty report

16. A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a…CVE-2026-106069nodejs · CVSS 7.4 · 0.3% likelycovered by CyberSIXT

    CWE-2951 bounty report1 article

17. A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with no…CVE-2026-105483nodejs · CVSS 7.4 · 0.3% likelycovered by CyberSIXT

    CWE-2951 bounty report1 article

18. A flaw in V8's string hashing mechanism causes integer-like strings to be hashed to their numeric value, making hash collisions trivially predictable. By crafting a request that c…CVE-2026-21717nodejs · CVSS 5.9 · 0.3% likely

    CWE-3281 bounty report

19. A flaw in Node.js TLS host verification can cause an attacker to bypass certification validation. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js…CVE-2026-48934nodejs · CVSS 4.3 · 0.3% likely

    CWE-2951 bounty report

20. Node.js is vulnerable to a certificate validation bypass in https.Agent via cross-policy TLS session reuseCVE-2026-123877nodejs · CVSS 6.8 · 0.2% likelycovered by CyberSIXT

    CWE-2951 article1 article this week: Node.js fixes HTTP/2 and TLS flaws exposing data and keys

21. Node.js is vulnerable to a per-host mTLS authorization bypass via a CA-only SNI context failing open to the default CACVE-2026-123867nodejs · CVSS 4.2 · 0.1% likelycovered by CyberSIXT

    CWE-2951 article1 article this week: Node.js fixes HTTP/2 and TLS flaws exposing data and keys

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.