Linux · Security advisory · July 29, 2025
RLSA-2025:8514: Security update for 3 packages
RLSA-2025:8514, released July 29, 2025, fixes 3 CVEs across 3 products. None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
3
None rated Critical
Exploited
0
None reported
Exploitation more likely
0
Vendor assessment
Highest EPSS
0.0082
57th percentile
Priority of the 3 CVEs
Patch now 0
Urgent 0
High 3
Routine 0
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| nodejs | rocky 8 | 1:20.19.2-1.module+el8.10.0+1988+437f3d23 |
| nodejs-nodemon | rocky 8 | 0:3.0.1-1.module+el8.10.0+1988+437f3d23 |
| nodejs-packaging | rocky 8 | 0:2021.06-4.module+el8.10.0+1667+4a788d89 |
CVEs this fix closes
| Priority | CVE | Title | Impact | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|---|
| High | CVE-2025-23166 | Node.js 20 and 3 others: Uncaught Exception | 7.5 | 0.0082 | None reported | |
| High | CVE-2025-23165 | Node.js 20 and 1 other: Missing Release of Memory after Effective Lifetime | 7.5 | 0.0056 | None reported | |
| High | CVE-2025-23167 | A flaw in Node.js 20's HTTP parser allows improper termination of HTTP/1 headers using `\r\n\rX` instead of the required `\r\n\r\n`. This inconsistency enables request smuggling, allowing attackers to bypass proxy-based access controls and submit unauthorized requests. The issue was resolved by upgrading `llhttp` to version 9, which enforces correct header termination. Impact: * This vulnerability affects only Node.js 20.x users prior to the `llhttp` v9 upgrade. | 7.5 | 0.0051 | None reported |
Showing 1 to 3 of 3
1