Docker image: update Node for CVE-2026-111497 (24.22.1)

未关闭
#581 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
65/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
docker
领域
devops

调研方向

Start by reading the Docker image definitions and checking how they install Node.js from Ubuntu Noble or an installer script. Identify the supported image build path and update it to use a patched Node release named in the issue, then build the image and confirm its runtime reports that version. Done when a new image tag ships with a patched Node runtime.

由索引模型根据 Issue 内容生成。

描述

I run the official 19.0-20260723 image, and the Node.js it ships is 18.19.1 (EOL, apt). 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. The published image gets Node from the base distribution or an installer script rather than a pinned official node tag (ubuntu noble apt nodejs 18; distro fix needed). Rebuilding on, or installing, Node 24.22.1 and cutting a new image tag would clear the vulnerable runtime. I am happy to open a pull request if you want one.

主要语言
Dockerfile
星标
1.2k
派生
1.7k
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

odoo/docker 的其他 Issue

查看 odoo/docker 的全部 Issue

相似的 Issue

更多 DevOps Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。