The Wire · Showcase
NODE 26.8.1 HITS DOCKER IMAGES
By RepoJournal · Filed · About Node.js
Node's official Docker images just caught up to the latest releases, and a pair of core patches landed that you need on your radar.
The official Node.js Docker images are now shipping Node.js 24.20.0 and 26.8.1 [1], a manual correction that fixes the broken `node -v` output on 26.8.0. In core, two security-policy changes landed: James Snell relaxed vulnerability handling for experimental features [2], while Rafael Gonzaga clarified triage dispositions and permission boundaries [3]. More critically for anyone running HTTP/2, Tim Perry fixed a write deadlock exposed by larger window sizes [4], removing a redundant guard added as a security mechanism. A quieter but valuable fix: `rmSync` now produces correct error messages for non-ASCII paths on Linux and Windows [5]. Test coverage for `Readable.from()` sync iterator errors [6] rounds out a steady 24 hours across 24 commits and 17 PRs.
One email a day. Unsubscribe in one click.
Keep up with Node.js in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Pull the official node:24.20.0 or node:26.8.1 Docker image for your next deploy nodejs/docker-node [immediate]
- → Watch for the http2 deadlock fix in your next Node release; it matters if you use large HTTP/2 windows nodejs/node [monitor]
- → Review the updated security triage policy for experimental features nodejs/node [plan]
References
- [1] feat: Node.js 24.20.0, 26.8.1 ↗ nodejs/docker-node
- [2] meta: refine the security vuln posture for experimental features nodejs/node
- [3] doc: clarify security triage dispositions and permission boundaries nodejs/node
- [4] http2: fix write deadlock exposed by larger window sizes nodejs/node
- [5] fs: fix rmSync error messages for non-ASCII paths nodejs/node
- [6] test: cover Readable.from() sync iterator errors ↗ nodejs/node