OpenClaw 2026.10.6 Goes Stable and Requires Patched Node After the eMudhra Certificate Key Compromise
The patch release carries beta-tested recovery fixes to stable and now requires Node builds that reject the eight compromised eMudhra certificate keys. Plus: Focus Weeks open the team server to contributors, Roboclaw's Baseten draft waits on a live test, a Node-first upgrade checklist and steipete's GitHub skill.
OpenClaw 2026.10.6 Goes Stable and Raises the Node Floor
The OpenClaw 2026.10.6 release notes on GitHub went up at 5:53 AM Pacific on Thursday, and npm's latest tag now points at 2026.10.6. Beta stays on 2026.10.10-beta.3. The notes call it a patch release of "focused reliability fixes only" with no new user-facing features, drawn from 293 pull requests merged since 2026.10.5.
The headline change is a hard runtime requirement. OpenClaw now needs Node 24.22.1 or newer on the 24 line, or 26.12.1 or newer on the 26 line, because those builds reject TLS chains signed with the compromised certificate keys covered by this week's Node.js security releases. Docker images ship Node 24.22.1, the installers pick the patched runtimes, and openclaw update stops with recovery guidance before installing onto an older Node rather than breaking a running install.
That work landed late Wednesday in pull request #179992 requiring patched Node and native pnpm runtimes, opened by joshavant at 3:39 PM Pacific and merged at 9:00 PM. It also pins source builds to pnpm 12.15.0, because the previously selected pnpm carried its own affected native TLS runtime. In its test runs, the official Node 24 and 26 builds rejected all 192 TLS attempts using the incident keys while ordinary HTTPS requests still succeeded.
Raising the runtime floor a day after an upstream security release is the right call for software that holds API keys and talks to many services over TLS. It also means 2026.10.6 is not a drop-in update everywhere. Hosts pinned to an older Node 24 or 26 build need a runtime change first, so plan the upgrade as two steps, not one.
Why the Floor Moved: Eight Compromised eMudhra Keys
The Node.js October 22, 2026 security release announcement shipped Node 22.23.4, 24.22.1 and 26.12.1 with a certificate-store update titled "eMudhra Intermediate CA Compromise". The same releases close several high-severity bugs, including a Brotli decoder flaw that Node says permits remote code execution.
The certificate fix itself is described in Node.js pull request #66871 blocking chains that contain known-bad public keys, merged on Tuesday. Node has no browser-style revocation list, so a chain through a compromised intermediate still verifies if it reaches a trusted root. The patch adds a compiled-in blocklist for the eight eMudhra and emSign intermediates whose private keys were reported compromised this month.
Two limits matter for operators. The pull request says sessions resumed from before the upgrade "are not re-verified," so restart services afterward. And because the block runs inside normal verification, code that sets rejectUnauthorized to false gets no protection from it. Node 22.23.4 has the fix too, but OpenClaw's documentation lists Node 22 as unsupported.
What Else 2026.10.6 Brings to Stable
Several fixes from yesterday's beta.3 story are now in stable, including recovery of held system-agent databases after schema changes (#176783), app-managed plugins converging on the installed core version (#174257) and long command deadlines through the macOS companion (#172117).
Beyond that, package swaps refuse unsafe service states, Doctor refuses malformed or lossy workspace imports, and queued turns and streamed replies survive Gateway restarts without disappearing or duplicating. WhatsApp, Telegram, Slack and Discord delivery fixes stop lost or duplicated messages. One authority change stands out: same-conversation follow-ups scheduled from an authorized operator turn now keep that operator's current authority when they run (#176422).
Two things are not there. The release's complete contribution record does not list #173862 or #174060, the fixes that closed the update-hang issue #173764 on main, or the three exit-78 manual-upgrade fixes (#178289, #178292, #178286).
For most fleets, 2026.10.6 is the update to take this week: it adds no features, and it contains the security floor plus restart-safe delivery fixes. Keep the manual Doctor sequence in your runbooks, though. The hang and exit-78 fixes still live on main and in the 2026.10.10 betas, not in this stable build.
Focus Weeks Open the Team Server to Outside Contributors
The OpenClaw blog post introducing Focus Weeks, published Wednesday, sets a new contribution rhythm. Each week the project picks one area of its roadmap, puts a maintainer on point and opens a public community thread where code, bug reports, testing and documentation all count. The first Focus Week runs October 19 to 25 on the Control UI, with Vyctor Brzezowski as the maintainer on point.
The second part is an experiment in working inside OpenClaw itself. A rotating group of contributors, which the project calls Clawtributors, gets temporary guest access to the shared OpenClaw Team environment, where people and their agents share sessions and context. "We're building OpenClaw with OpenClaw," the post says. Team access is invite-only for now, but the public thread is open to anyone.
Pointing the first Focus Week at the Control UI makes sense, since the dashboard has just moved from Lit to Solid 2.0, largely through agent-written pull requests, as we reported yesterday. That rewrite needs human eyes on keyboard navigation and odd setups. If your team depends on the dashboard, this week is the cheapest moment to get your rough edges onto the maintainers' list.
Roboclaw Drafts Baseten Decision Models in Public, and Stops at the Live Test
The project's own agent, Roboclaw, opened draft pull request #179819 adding Baseten's elephant-1 and mammoth-1 decision models on Wednesday, after Vincent Koc (@vincentkoc) asked for it on X. It adds both as decision-only models under the existing Baseten credential, kept out of the chat catalog, and is still an unmerged draft.
The reason is a rule, not a test failure. The public Roboclaw session log for the Baseten decision-model work shows the agent marking itself blocked because no Baseten key was available, citing the repository's testing policy that "external APIs require live contract proof."
Also new from the project: ClawCast episode 14 on NVIDIA RTX Spark and local AI, recorded Wednesday with NVIDIA's Apoorv Chaudhary, on when local models are enough and when a frontier model still makes sense.
The useful signal here is the gate, not the models. An agent that writes an integration in an afternoon but refuses to call it done without a live call against the real API is the behavior teams should copy in their own pipelines. Ask your agents to label unverified work as unverified, every time.
Security Practice: Upgrade Node First, Then OpenClaw, Then Restart
Move every Gateway host to a patched Node runtime before taking 2026.10.6
The OpenClaw Node.js runtime requirements page now lists Node 24.22.1 or later and Node 26.12.1 or later, with Node 26 recommended, and says those releases "reject the keys compromised in the October 2026 eMudhra incident." Node 22, 23 and 25, and Node 24 or 26 builds below those versions, are unsupported.
- Run
node -von every host, including the Node recorded in a managed Gateway service, which can differ from the one on your PATH. - Upgrade Node before updating OpenClaw. The docs warn that doing it the other way round risks SQLite TEXT truncation.
openclaw updatechecks the target release's Node requirements first and can pick a compatible installed Node or provision a verified private runtime, but external schedulers and pinned crontab paths stay your job.- Restart the Gateway after the runtime change. Node's own patch notes that TLS sessions resumed from before the upgrade are not re-verified.
Skill Card: steipete's GitHub Skill for Focus Week Triage
@steipete/github, a short guide that teaches agents the gh command line
The GitHub skill listing by Peter Steinberger on ClawHub shows version 1.0.0 under the MIT-0 license with a passing ClawHub security audit, installable with openclaw skills install @steipete/github. Its SKILL.md teaches gh issue, gh pr, gh run and gh api, from checking CI on a pull request to viewing only a run's failed steps. ClawHub's public API reports 202,051 downloads and 7,654 installs.
Use the scoped name. When we asked ClawHub's API for the unscoped slug github, it refused with an ambiguous-slug error listing seven different skills by that name. Semgrep's OpenClaw Security Engineer's Cheat Sheet from Semgrep, recirculating on X this week but last updated in February, lists red flags to check in any lookalike: external-download prerequisites, base64-encoded commands, curl | bash patterns, password-protected archives and auto-update behavior.
A popular, plain-text skill from the project's own maintainer is about as low-risk as ClawHub gets, but the agent inherits whatever your gh login can do. Give it a fine-grained token scoped to the repositories you actually work on, and never install a same-named copy from an unfamiliar publisher.
Rolling out OpenClaw 2026.10.6?
SEN-X helps teams inventory the Node runtime on every Gateway host, stage the Node-first upgrade order, keep Doctor runbooks current and vet ClawHub skills before agents install them.
Contact SEN-X →