Finding / openclaw
2026-10-24-openclaw-stable-now-requires-the-october-patched-node-runtime
Stable now requires the October-patched Node runtime. Stable raised its runtime floor to Node 24.22.1 on the 24 line or 26.12.1 and later. Installers and Docker moved to patched runtimes; the updater checks before staging an incompatible candidate. The release connects this to compromised certificate keys addressed by Node’s October security updates. This is runtime exposure reduction, not a demonstrated OpenClaw-specific exploit. Source builds also changed to pnpm 12.15.0.
Channel: tagged-release. Half: defect. Date: 2026-10-22.
Operator consequence: Upgrade Node before moving a manually managed Gateway to 10.7. Check the service’s runtime, not just the interactive shell’s node. Do not select beta or extended-stable on the assumption that their lower engine minimum proves an equally patched bundled runtime. The admission check makes a bad update fail earlier; operators still own runtime inventory.
Receipt
Finding metadata
Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0
Finding ID: 2026-10-24-openclaw-stable-now-requires-the-october-patched-node-runtime
Source links
Primary links, including exact changelog lines when available.
- commit2026-10-24-openclaw-stable-now-requires-the-october-patched-node-runtimegithub.com/openclaw/openclaw/commit/a9088826651c6b9136f9b5e9105c341a34ce3bd2tagged commit file2026-10-24-openclaw-stable-now-requires-the-october-patched-node-runtimeopenclaw/openclaw / package.jsongithub release2026-10-24-openclaw-stable-now-requires-the-october-patched-node-runtimeopenclaw/openclaw / v2026.10.6official docs2026-10-24-openclaw-stable-now-requires-the-october-patched-node-runtimenodejs.org/en/blog/vulnerability/october-2026-security-releases