Repository navigation
Docker image: bump Node to 24.22.1 (CVE-2026-111497) - #3684
mahfuz-rahman007 wants to merge 2 commits into
Conversation
|
|
2 similar comments
|
|
|
|
{{ message }}
Open
mahfuz-rahman007 wants to merge 2 commits into
Open
mahfuz-rahman007 wants to merge 2 commits into
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I run the official release.2026-08-19T02-25-59Z.2698 image, and the Node.js it ships is 24.19.0. That build is affected by CVE-2026-111497, a vulnerability in Node's Brotli decoder that can lead to remote code execution, fixed on 21 October 2026 in Node 22.23.4, 24.22.1, and 26.12.1 (https://nodejs.org/en/blog/vulnerability). Node 14, 16, 18, 19, 20, 21, 23, and 25 are end of life and will not get this patch, so the runtime needs to be on 22.23.4, 24.22.1, or 26.12.1. In dockers/teable/Dockerfile, the image is still based on ARG NODE_VERSION=24.19.0. Updating that to ARG NODE_VERSION=24.22.1 and publishing a new release would ship a patched runtime. The patch below is only that version bump. Happy to adjust the suffix if you prefer another patched line (22.23.4, 24.22.1, or 26.12.1).