OpenClaw Which Version to Follow and How to Upgrade
Xiao Zhou installed OpenClaw on a small company server, and it ran fine for a month without him touching it. One day someone in the group chat forwarded a message: "OpenClaw has a high-severity vulnerability—upgrade right away." He opened GitHub and found several releases published within a week, plus a line called extended-stable, and for a moment didn't know which one to upgrade to, or how to roll back if the upgrade went wrong.
This lesson walks through the process in the real order:
- 1?
- 2?
- 3?
- 4?
- 5?
- 6?
Click them one by one, in order.
OpenClaw has four update channels: stable, extended-stable, beta, and dev. Most people follow stable; those who want less hassle and long-term server operation can follow extended-stable; beta and dev are for people who want to try new things and for developers. When a security advisory comes out, upgrade to the fixed version stated in the advisory—or a newer one—within your own channel.
What You'll Be Able to Do After This Lesson
- Explain the differences between the four channels and pick one for your machine
- Read a OpenClaw security advisory and determine whether you're affected
- Dry-run, upgrade, and verify with
openclaw update, and roll back if necessary
First, Deal with the Advisory at Hand
2026-11-19, OpenClaw published a high-severity advisory, GHSA-pw3x-g8v8-fvj2 (CVSS 8.8). It affects this tutorial's baseline version, 2026.10.9, so here's the conclusion up front:
| Field in the advisory | Content |
|---|---|
| Title | OpenClaw delegation could skip approval for restricted agents |
| Issue | When the tool policy forbids executing commands and writing files, the openclaw tool can still write persistent configuration without approval, which a restricted agent can use to open up host command execution |
| Affected versions | ≥ 2026.9.2 and < 2026.10.33; ≥ 2026.11.1 and < 2026.11.4 |
| Fixed versions | The first fixed version on stable is 2026.11.4; extended-stable users should upgrade to 2026.10.33 |
| Mitigation before upgrading | Set tools.exec.mode to ask to reject untrusted delegation changes |
Original advisory: https://github.com/openclaw/openclaw/security/advisories/GHSA-pw3x-g8v8-fvj2. All OpenClaw security advisories are on the repository's Security → Advisories page: https://github.com/openclaw/openclaw/security/advisories.
Look it upMy current version is...
Click one to see.
There's one sentence in the advisory that's easy to miss: this vulnerability "does not change OpenClaw's trust model"; how big the impact is depends on your configuration and whether low-trust input can reach this path. In other words, a Gateway used by only one person with no external channels attached carries lower risk, but you should still upgrade.
- I've checked my version with
openclaw --versionand know whether I'm affected
What's the Difference Between the Four Channels
The official documentation's definitions of the four channels:
| Channel | Corresponding npm tag | Description |
|---|---|---|
| stable | latest | Recommended for most users |
| extended-stable | extended-stable | The official wording is "trailing supported-month package channel", i.e., a version line that trails the latest release and is maintained monthly; only package installs (npm, etc.) are supported, not git installs; installation can only be done in the foreground; when update.checkOnStart is enabled, it only shows a read-only update notice—it never installs automatically |
| beta | beta | Takes whichever of beta and latest has the newer version number; an older beta will not replace a newer stable |
| dev | None (the git main branch) | May contain unfinished features or breaking changes; do not use on a production Gateway |
extended-stable's positioning is stated most plainly in 2026.10.33's release notes: "gateway-only extended-stable release, which is our current equivalent to LTS". It's the end-of-10 OpenClaw, plus critical security fixes, reliability and performance fixes, and new model support. It only ships the Gateway: the npm core package, the accompanying official npm plugins, and the Gateway Docker image—not the native App. As for version numbers, extended-stable uses patch numbers from 33 and above each month (e.g., 2026.9.33 ~ 2026.9.37, 2026.10.33), numbered separately from stable.
As of 2026-11-20, the latest versions on the three lines:
| Channel | Version | Date |
|---|---|---|
| stable | 2026.11.6 | 2026-11-19 |
| extended-stable | 2026.10.33 | 2026-11-18 |
| beta | 2026.11.10-beta.1 | 2026-11-19 |
Quiz timeXiao Zhou's OpenClaw is installed on a server via npm, running only the Gateway. He doesn't want to track changes weekly, but doesn't want to miss a single security fix either. Which channel is a better fit?
- I've chosen the channel I'll follow
Step 1: Find Out Your Current Version and Channel
Why: before upgrading you need to know your starting point, especially which installation the Gateway service is actually running.
openclaw --version
openclaw update statusYou should see: the first command prints the CLI's version number. The second shows the current channel and the source that determines it (configuration, git tag, git branch, installed version, or default), the installation method (git or package), the current version, and whether updates are available.
The official pre-upgrade check also reminds you: openclaw --version reports the command-line version, and the Gateway service may point to a different installation. Double-check with openclaw status and openclaw gateway status --deep.
- I know my version, channel, and installation method
Step 2: If You Can't Upgrade Right Away, Apply a Temporary Mitigation First
Why: the advisory's mitigation is to route execution through manual confirmation, blocking the most dangerous path before you upgrade.
In ~/.openclaw/openclaw.json:
{
tools: {
exec: { mode: "ask" },
},
}Restart the Gateway after the change. This is only a mitigation; the advisory's first recommendation is still to upgrade.
- For machines that can't be upgraded yet, I've set
tools.exec.modetoask
Step 3: Back Up, Then Dry-Run
Why: the official documentation says what openclaw update saves automatically is only a copy of the pre-upgrade configuration, not the full state. Downgrading doesn't undo configuration and database migrations either; if you truly need to go back to the old version, what you rely on is a pre-upgrade backup.
mkdir -p ~/Backups/openclaw
openclaw backup create --output ~/Backups/openclaw --verifyYou should see: an archive file appears in the backup directory. The archive may contain credentials and channel state—protect it the way you'd protect ~/.openclaw.
Then dry-run it to see what it plans to do:
openclaw update --channel stable --dry-run
# 想跟 extended-stable 的改成:
openclaw update --channel extended-stable --dry-runYou should see: the report shows the active channel, the target version, the actions planned to run, and whether a downgrade confirmation is needed.--dry-run changes nothing.
- I have a backup with
--verifyand have reviewed the dry-run results
Step 4: Upgrade and verify
Why: --channel performs the upgrade, and after the core upgrade succeeds it writes your choice into the update.channel in the config, so that simply running openclaw update afterwards follows this same track.
openclaw update --channel stable
# 或
openclaw update --channel extended-stableYou should see: the upgrade completes. For managed Gateway services, once the switch succeeds it refreshes the service and checks readiness; if the switch is rejected or rolled back after verification, the previous service is restored.
Double-check once more:
openclaw --version
openclaw gateway status --deepYou should see: the version number is 2026.11.4 or newer (stable), or 2026.10.33 (extended-stable).
A few things to watch out for:
git installs cannot use extended-stable. OpenClaw stays as is, letting you switch to a package install.
Switching to extended-stable 2026.10.33 from 2026.11.1 ~ 11.3 is a downgrade by version number, so a downgrade confirmation will appear. The downgrade does not undo migrations that have already happened; in this case it is safer to go from stable to 2026.11.4 or above.
If you just want to install a specific version once without changing the channel, use
--tag, for exampleopenclaw update --tag 2026.4.1-beta.1from the official docs.--tagonly works for npm package installs; git installs ignore it.The version shown by
openclaw --versionis no longer in the affected range
Step 5: Roll back if something goes wrong
Why: new versions sometimes conflict with your environment. The official recommendation is to roll back with openclaw update rather than manually overwriting with npm i -g, because the latter does not keep the previous package and does not run the recovery process.
openclaw update --tag <已知可用的版本> --dry-run
openclaw update --tag <已知可用的版本>The updater checks compatibility and asks you to confirm the downgrade. If your saved channel is extended-stable, the official docs say you need to add --channel stable to specify an exact version.
You should see: the service restarts and the running version goes back to the one you specified. If the old version cannot read the current state, the updater refuses; in that case restore the backup from Step 3 together with the corresponding old version. Do not bypass refusals like "config or database written by a newer version."
There are two more fallbacks:
- When validation of a newly activated package fails,
openclaw updateautomatically rolls back to the previous version if conditions are met. From 2026.11.5 onward, a failed Doctor or Gateway startup also rolls back the activated update. - If you get stuck, run
openclaw triageon the machine where the Gateway lives; it hands diagnostic information to the local coding agent to help you fix things.
When rolling back, do not go back to an affected version
Because for the GHSA-pw3x rollback, the target version must be 2026.11.4 or above, or 2026.10.33. Going back to 2026.10.9 is equivalent to reinstalling the vulnerability.
- I have noted down a version number that is "known to work and unaffected by the advisory"
Checkpoint
- I can state two differences between stable and extended-stable (e.g., update cadence, whether native Apps are included)
- I can find the affected versions, fixed versions, and temporary mitigations from an advisory
- My Gateway has been upgraded to 2026.11.4 or above, or 2026.10.33
- I know that before upgrading I should first
openclaw backup create --verify, then--dry-run
Common misconceptions
Assuming extended-stable updates itself. It never installs automatically; at most it gives a hint during the startup check. Anyone on this track needs to check advisories regularly and run openclaw update manually.
Assuming a downgrade can undo everything. The official docs state clearly that downgrade packages do not undo config and database migrations. When the state has already been migrated to a format the old version cannot read, the only supported approach is restoring the pre-upgrade backup.
Assuming beta is safer because it is "newer" than stable. beta is a candidate release; security fixes land in stable and extended-stable. Use stable or extended-stable in production; the docs explicitly say dev must not be used on a production Gateway.
Next section
Common commands and config options are summarized in CLI Commands & Config Quick Reference, and changes across versions are in Changelog.