CVE-2025-27209 – Node.js V8 HashDoS Vulnerability

CVE ID : CVE-2025-27209

Published : July 18, 2025, 11:15 p.m. | 1 hour, 40 minutes ago

Description : The V8 release used in Node.js v24.0.0 has changed how string hashes are computed using rapidhash. This implementation re-introduces the HashDoS vulnerability as an attacker who can control the strings to be hashed can generate many hash collisions – an attacker can generate collisions even without knowing the hash-seed.

* This vulnerability affects Node.js v24.x users.

Severity: 7.5 | HIGH

Visit the link for more details, such as CVSS details, affected products, timeline, and more…

Read More

CVE-2025-27210 – Node.js Windows Path Join API Incomplete Fix Vulnerability

CVE ID : CVE-2025-27210

Published : July 18, 2025, 11:15 p.m. | 1 hour, 40 minutes ago

Description : An incomplete fix has been identified for CVE-2025-23084 in Node.js, specifically affecting Windows device names like CON, PRN, and AUX.

This vulnerability affects Windows users of `path.join` API.

Severity: 7.5 | HIGH

Visit the link for more details, such as CVSS details, affected products, timeline, and more…

Read More

CVE-2025-7394 – OpenSSL wolfSSL Predictable Random Number Generation After Fork Vulnerability

CVE ID : CVE-2025-7394

Published : July 18, 2025, 11:15 p.m. | 1 hour, 40 minutes ago

Description : In the OpenSSL compatibility layer implementation, the function RAND_poll() was not behaving as expected and leading to the potential for predictable values returned from RAND_bytes() after fork() is called. This can lead to weak or predictable random numbers generated in applications that are both using RAND_bytes() and doing fork() operations. This only affects applications explicitly calling RAND_bytes() after fork() and does not affect any internal TLS operations. Although RAND_bytes() documentation in OpenSSL calls out not being safe for use with fork() without first calling RAND_poll(), an additional code change was also made in wolfSSL to make RAND_bytes() behave similar to OpenSSL after a fork() call without calling RAND_poll(). Now the Hash-DRBG used gets reseeded after detecting running in a new process. If making use of RAND_bytes() and calling fork() we recommend updating to the latest version of wolfSSL. Thanks to Per Allansson from Appgate for the report.

Severity: 0.0 | NA

Visit the link for more details, such as CVSS details, affected products, timeline, and more…

Read More