|
| 1 | +--- |
| 2 | +date: 2026-06-09T22:00:00.000Z |
| 3 | +category: vulnerability |
| 4 | +title: Wednesday, June 17, 2026 Security Releases |
| 5 | +slug: june-2026-security-releases |
| 6 | +layout: blog-post |
| 7 | +author: The Node.js Project |
| 8 | +--- |
| 9 | + |
| 10 | +# Summary |
| 11 | + |
| 12 | +The Node.js project will release new versions of the 26.x, 24.x, 22.x |
| 13 | +releases lines on or shortly after, Wednesday, June 17, 2026 in order |
| 14 | +to address one or more security issues, the highest severity is HIGH. |
| 15 | + |
| 16 | +## Impact |
| 17 | + |
| 18 | +The highest severity issue fixed in the 26.x release line is HIGH. |
| 19 | +The highest severity issue fixed in the 24.x release line is HIGH. |
| 20 | +The highest severity issue fixed in the 22.x release line is HIGH. |
| 21 | + |
| 22 | +It's important to note that End-of-Life versions are always affected when a security release occurs. |
| 23 | +To ensure your system's security, please use an up-to-date version as outlined in our |
| 24 | +[Release Schedule](https://github.com/nodejs/release#release-schedule). |
| 25 | + |
| 26 | +## Release timing |
| 27 | + |
| 28 | +Releases will be available on, or shortly after, Wednesday, June 17, 2026. |
| 29 | + |
| 30 | +## Contact and future updates |
| 31 | + |
| 32 | +The current Node.js security policy can be found at <https://nodejs.org/en/security/>. |
| 33 | +Please follow the process outlined in <https://github.com/nodejs/node/blob/master/SECURITY.md> if |
| 34 | +you wish to report a vulnerability in Node.js. |
| 35 | + |
| 36 | +Subscribe to the low-volume announcement-only nodejs-sec mailing list at |
| 37 | +<https://groups.google.com/forum/#!forum/nodejs-sec> to stay up to date on security vulnerabilities |
| 38 | +and security-related releases of Node.js and the projects maintained in the nodejs GitHub organization. |
0 commit comments