Skip to content

fix: make version refs consistent in the blog post #8554

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
aduh95 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: make version refs consistent in the blog post #8554

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions apps/site/pages/en/blog/vulnerability/december-2025-security-releases.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ author: The Node.js Project

## Security releases available

Updates are now available for the 25.x, 24.x, 22.x, 20.x Node.js release lines
Updates are now available for the 25.x, 24.x, 22.x, and 20.x Node.js release lines
to address:

- 3 high severity issues.
Expand Down Expand Up @@ -47,7 +47,7 @@ expected isolation guarantees and enables arbitrary file read/write, leading to

Impact:

- This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25.
- This vulnerability affects users of the permission model on Node.js 20.x, 22.x, 24.x, and 25.x.

Thank you, to natann for reporting this vulnerability and thank you RafaelGSS for fixing it.

Expand All @@ -68,7 +68,7 @@ server.on('secureConnection', socket => {

Impact:

- This vulnerability affects all users in active release lines: 20.x, 22.x, 24.x, 25.x
- This vulnerability affects all users in active release lines: 20.x, 22.x, 24.x, and 25.x

Thank you, to dantt for reporting this vulnerability and thank you RafaelGSS for fixing it.

Expand All @@ -90,7 +90,7 @@ for details.

Impact:

- This vulnerability affects all users in active release lines: 20.x, 22.x, 24.x, 25.x
- This vulnerability affects all users in active release lines: 20.x, 22.x, 24.x, and 25.x

Thank you, to Andrew MacPherson (AndrewMohawk) for identifying & aaron_vercel for reporting this vulnerability and thank you mcollina for fixing it.

Expand All @@ -103,10 +103,10 @@ TLS connections. Over time this can lead to resource exhaustion and denial of se

Impact:

- This vulnerability was already fixed on Node.js v24.12.0. It has no impact on
- This vulnerability was already fixed on Node.js 24.12.0. It has no impact on
other active release lines.

This public CVE is only issued for the affected v24 releases.
This public CVE is only issued for the affected 24.x releases.

Thank you, to giant_anteater for reporting this vulnerability and thank you RafaelGSS for fixing it.

Expand All @@ -122,7 +122,7 @@ In the moment of this vulnerability, network permissions (`--allow-net`) are sti

Impact:

- The issue affects users of the Node.js permission model on version v25.
- The issue affects users of the Node.js permission model on Node.js 25.x.

Thank you, to mufeedvh for reporting this vulnerability and thank you RafaelGSS for fixing it.

Expand Down Expand Up @@ -152,7 +152,7 @@ ways that obscure activity, reducing the reliability of logs.

Impact:

- This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25.
- This vulnerability affects users of the permission model on Node.js 20.x, 22.x, 24.x, and 25.x.

Thank you, to oriotie for reporting this vulnerability and thank you RafaelGSS for fixing it.

Expand All @@ -165,7 +165,7 @@ Thank you, to oriotie for reporting this vulnerability and thank you RafaelGSS f

# Summary

The Node.js project will release new versions of the 25.x, 24.x, 22.x, 20.x
The Node.js project will release new versions of the 25.x, 24.x, 22.x, and 20.x
releases lines on or shortly after, Monday, December 15, 2025 in order to address:

- 3 high severity issues.
Expand Down
Loading