Repository navigation
Conversation
Closes usesend#473. - docker/Dockerfile: node:22-alpine3.20 -> node:22-alpine3.23. The 3.20 tag stopped receiving updates, so rebuilds stayed on Node 22.16.0, which is affected by the 21 Oct 2026 Node.js security release (CVE-2026-111497, Brotli decoder RCE). The image now builds on 22.23.4. - next 15.5.27 -> 15.5.28 (apps/web, apps/marketing) for the 14 Oct 2026 Next.js security release: image optimization RCE with SVG (GHSA-2464-fhr4-w9xw) and Server Actions DoS (GHSA-p3m5-59mp-jv5r). - Override sharp 0.34.x -> 0.35.5. next 15.5.28 accepts `^0.34.3 || ^0.35.5`, so without the override the lockfile kept 0.34.5, below the version the image-optimization advisory names. Co-Authored-By: Claude Opus 5.5 <[email protected]>
|
Someone is attempting to deploy a commit to the kmkoushik's projects Team on Vercel. A member of the Team first needs to authorize it. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
No actionable comments were generated in the recent review.
|
|
Thanks a lot @jiaweing, this was a clear and well-researched write-up. Your changes (the |
Closes #473.
The published self-hosted image (
v1.9.8/latest) and a rebuild of currentmainare both still exposed to the October 2026 Node.js and Next.js security releases. This PR fixes the three gaps described in #473.Changes
docker/Dockerfilebasenode:22-alpine3.20(Node 22.16.0, tag no longer updated)node:22-alpine3.23(Node 22.23.4)engines/CI but not the image, so the image would have stayed on 22.16.0.next(apps/web,apps/marketing)sharp[email protected]accepts^0.34.3 || ^0.35.5, so the lockfile otherwise keeps 0.34.5. 0.35.5 is the version the image-optimization advisory names. The override is scoped to>=0.34.0 <0.35.5and added in bothpnpm-workspace.yamlandpackage.json, following the existing sync comment.pnpm-lock.yamlwas regenerated with the pinned[email protected].Verified
docker build -f docker/Dockerfile .succeeds.node -v→v22.23.4,next15.5.28,sharp0.35.5.Once merged, cutting a release would get these fixes to self-hosters, who are still on Next.js 15.5.18 and Node 22.16.0 in
v1.9.8.🤖 Generated with Claude Code
Summary by cubic
Closes #473 by patching the three October 2026 security gaps in the self-hosted image: Node.js, Next.js, and sharp.
node:22-alpine3.20(Node 22.16.0, a tag that stopped updating) →node:22-alpine3.23(Node 22.23.4). Fixes CVE-2026-111497 (Brotli decoder RCE) and the rest of the 21 Oct 2026 Node.js release.apps/webandapps/marketing. Fixes the 14 Oct 2026 release: image optimization RCE with SVG (GHSA-2464-fhr4-w9xw) and Server Actions DoS (GHSA-p3m5-59mp-jv5r).sharp0.34.5 → 0.35.5 via a pnpm override scoped to>=0.34.0 <0.35.5, added inpnpm-workspace.yamlandpackage.json. Without it, next 15.5.28's range (^0.34.3 || ^0.35.5) keeps the lockfile on 0.34.5, below the version the advisory names.The image builds and verified node v22.23.4, next 15.5.28, sharp 0.35.5 (native binary loads and renders a PNG on Alpine 3.23). The full app wasn't run since the entrypoint needs a database for Prisma migrations. Cutting a release after merge would get these fixes to self-hosters on
v1.9.8(Next.js 15.5.18, Node 22.16.0).Written for commit a7239ad. Summary will update on new commits.
Summary by CodeRabbit