Repository navigation
fix(deps): patch October 2026 Next.js, sharp and Node.js CVEs - #119
Conversation
- next 15.5.27 -> 15.5.28 (GHSA-p3m5-59mp-jv5r, CVE-2026-96889) - override sharp to ^0.35.5: next@15.5.28 still accepts sharp 0.34, which keeps the vulnerable SVG decoder (CVE-2026-96889) - pin engines.node to the Oct 21 Node.js security releases (CVE-2026-111497 Brotli RCE and 9 others) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
🚅 Deployed to the website-frontend-pr-119 environment in website-frontend
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
Summary
sharpoverride^0.35.5: next@15.5.28 still acceptssharp ^0.34.3, and our lockfile hadsharp@0.34.5, which is still vulnerable to CVE-2026-96889. The lockfile now resolves0.35.5.engines.node: ^22.23.4: Oct 21 Node.js security releases (CVE-2026-111497 Brotli RCE and 9 others). Production was stuck on 22.23.3: with no version source, Railpack reuses the "previous installed version". Withengines.nodeset, Railpack resolves the major version (22) and installs the newest 22.x on each build.Deploy notes
package.json/bun.lockbare inrailway.jsonwatchPatterns, so the build triggers once this reaches the deployed branch.package.json > engines > node. If it still says "previous installed version", setRAILPACK_NODE_VERSION=22.Test plan
bun installandbun pm ls --allshownext@15.5.28andsharp@0.35.5bun run buildpassesnext/image-heavy pages (blog, chains) after deploy🤖 Generated with Claude Code
Summary by CodeRabbit