OpenClaw 2026.10 Security Fixes: Release Security Notes for 2026.10.1 to 2026.10.5

Published 2026-10-19 · Updated 2026-11-01 · By The Is My Agent Safe team

Short answer

Update to 2026.10.5 (latest). OpenClaw's security advisories list has no advisory with a first fix in 2026.10.1 to 2026.10.5, but each release's notes include security and privacy fixes: credential masking in long tool output, Tlon group-DM permissions, saved sign-ins during Doctor repairs, and more access checks in 2026.10.5. 2026.10.5 also adds public conversation links that anyone with the link can read.

  • Update to 2026.10.5, the latest stable release (October 18, 2026). It also carries the security fixes listed for 2026.10.2 to 2026.10.4.
  • No OpenClaw security advisory lists a first fix in 2026.10.1 to 2026.10.5 (checked October 19, 2026). If your OpenClaw version is below 2026.8.1, you're missing fixes for advisories rated high. 2026.10.5 covers the ones in the OpenClaw package; check separately versioned channel plugins against the advisories list too.
  • If you publish a conversation link in 2026.10.5, anyone with the link can read it without signing in, including future messages.
  • After upgrading, confirm the version, re-run openclaw security audit --deep, and follow any release-specific step below (Gateway restart for the secret egress proxy, Tlon DM resends).

Paste your audit: run openclaw security audit --deep and paste the output into our free check for a red/amber/green result with the most important finding first (Limits of the check).

Update to 2026.10.5 (latest). It's the newest stable OpenClaw release, published on GitHub on October 18, 2026, and it also carries the security fixes listed for 2026.10.2 to 2026.10.4.

Everything here comes from two official sources, linked for each release below:

Newest release first. Each one lists what changed for security (from the "Security and privacy" part of its notes), who it affects, whether you need to act, and what to check after upgrading. Dates are GitHub release dates (UTC). For 2026.10.1, the items come from the changelog's "Security and privacy" bullet. The formatted release notes group a longer Security and Privacy section differently.

Advisories and the 2026.8.1 floor

As of October 19, 2026, no advisory on OpenClaw's security advisories list names 2026.10.1, 2026.10.2, 2026.10.3, 2026.10.4 or 2026.10.5 as its first fixed version. The newest advisories there were published September 11, 2026. So none of the fixes below comes with a CVE or a severity rating from OpenClaw.

If your OpenClaw version is below 2026.8.1, you're missing fixes for advisories rated high. Updating straight to 2026.10.5 covers the ones in the OpenClaw package. Some 2026.8.1 fixes are in separately versioned channel plugins (@openclaw/whatsapp, slack, matrix and voice-call), so check those against the advisories list too. Our guide to updating without breaking things has the back-up and dry-run steps.

2026.10.5 (latest), October 18, 2026

Official: release · release notes · changelog · Advisories: none list this release as the first fix.

A large release (2,250 pull requests). Its security and privacy section repeats the fixes from 2026.10.2 to 2026.10.4 and adds more.

New: public conversation links. A published conversation now opens at its normal chat address, and anyone with the link can read the transcript without signing in. OpenClaw's notes say the link exposes existing and future user messages and final replies, redaction is best effort, and turning sharing off can't recall saved copies. Deployments behind a login proxy need OpenClaw's public-reader route setup, with private app and API routes kept behind the login.

Security and privacy fixes (selected):

Who it affects: everyone on an earlier version. The public-link change matters if you or your users publish conversations.

Do you need to act? Update. Before you publish a conversation, review it. If your Gateway sits behind a login proxy, follow the public-reader route setup before anyone uses public links.

What to check after upgrading:

  1. Run openclaw --version and confirm it shows 2026.10.5.
  2. If you use the secret egress proxy, restart the Gateway and start new commands (from the notes).
  3. If you use Tlon, ask senders of DMs that were pending before the update to resend them after you approve.
  4. Re-run openclaw security audit --deep and work through any new findings.

2026.10.4, October 16, 2026

Official: release · release notes · changelog · Advisories: none list this release as the first fix.

Security and privacy fix: in Tlon group DMs, an unverified claim about who wrote a message no longer gives owner commands, approval or admin actions, or elevated tool permissions. The notes add a limit: a group member can still pose as an allowed sender to chat with the agent, and replies go to that sender's private conversation.

Who it affects: people who connect OpenClaw to Tlon.

Do you need to act? If you use Tlon, update. After you approve a DM that was pending before the update, ask the sender to resend it.

What to check after upgrading: confirm the version, then check Tlon DMs that were pending before the update and ask for resends.

2026.10.3, October 13, 2026

Official: release · release notes · changelog · Advisories: none list this release as the first fix.

Security and privacy fix: an unreadable legacy auth file no longer makes a Doctor cleanup discard your saved OAuth sign-ins. Doctor now names the file to inspect or restore before you retry. Sign-ins that were already deleted aren't restored.

Who it affects: people who run Doctor repairs on installs with older auth files.

Do you need to act? Update before running Doctor repairs. If Doctor names an auth file, inspect or restore it before retrying (Doctor state recovery guidance).

What to check after upgrading: confirm the version. If an earlier update was blocked, the notes point to the manual recovery step in OpenClaw's updating guide.

2026.10.2, October 12, 2026

Official: release · release notes · changelog · Advisories: none list this release as the first fix.

Security and privacy fixes:

Who it affects: anyone who relies on credential masking in tool output, and people who use the secret egress proxy.

Do you need to act? Update. If you use the secret egress proxy, restart the Gateway and start a new command afterward.

What to check after upgrading: confirm the version. The notes say an older CLI can still show a missing-module error during its first upgrade; run openclaw update status from the new install to check the result.

2026.10.1, October 10, 2026

Official: release · release notes · changelog · Advisories: none list this release as the first fix.

Security and privacy fixes:

Who it affects: anyone on an earlier release line. The notes don't say whether later 2026.9.x maintenance releases include these fixes.

Do you need to act? Update, but go straight to 2026.10.5: 2026.10.2 fixed a cleanup error on the first upgrade from 2026.10.1.

What to check after upgrading: confirm the version, then re-run openclaw security audit --deep.

Check your version and settings

Our free check is paste-only. You paste openclaw security audit --deep output and openclaw --version (and, if you choose, your config file). It puts the most important finding from OpenClaw's audit first, in plain English, flags risky settings and compares your version against published security advisories. Every finding explained, with fixes in order, is in the $29 full report. It's look-only and point-in-time, and green means no issues found in the checks we ran.

It does not detect malicious skills or review skill or MCP server code. See Limits of the check. Not live yet: agency features, with a preview planned for early November.

Where next

Frequently asked questions

Which OpenClaw version should I be on?

2026.10.5, the latest stable release on GitHub (October 18, 2026). Beta builds such as 2026.10.10-beta.2 are prereleases, so this page doesn't cover them.

Do the 2026.10.x releases fix any CVEs or GitHub security advisories?

Not according to OpenClaw's security advisories list as of October 19, 2026. The newest advisories there were published September 11, 2026, and none lists a 2026.10.x release as its first fixed version. The release notes do list security and privacy fixes, summarized on this page.

Where does 2026.8.1 fit in?

It's the release where OpenClaw's advisories list the most recent fixes rated high for the OpenClaw package. If your OpenClaw version is below it, update. Updating straight to 2026.10.5 covers the ones in the OpenClaw package. Some 2026.8.1 fixes are in separately versioned channel plugins (@openclaw/whatsapp, slack, matrix and voice-call), so check those against the advisories list too.

Is a published conversation link private?

No. OpenClaw's 2026.10.5 notes say anyone with the link can read the transcript without signing in, the link exposes existing and future user messages and final replies, redaction is best effort, and turning sharing off can't recall saved copies.

Does your free check tell me if I need to update?

Yes, for the version part. Paste openclaw --version with your audit output and the check compares your version against published security advisories. It doesn't detect malicious skills or review skill or MCP server code.

Sources

  1. OpenClaw GitHub releases
  2. OpenClaw GitHub security advisories
  3. OpenClaw release v2026.10.5 (GitHub, Oct 18, 2026)
  4. OpenClaw 2026.10.5 release notes (docs)
  5. OpenClaw 2026.10.5 changelog
  6. OpenClaw release v2026.10.4 (GitHub, Oct 16, 2026)
  7. OpenClaw 2026.10.4 release notes (docs)
  8. OpenClaw 2026.10.4 changelog
  9. OpenClaw release v2026.10.3 (GitHub, Oct 13, 2026)
  10. OpenClaw 2026.10.3 release notes (docs)
  11. OpenClaw 2026.10.3 changelog
  12. OpenClaw release v2026.10.2 (GitHub, Oct 12, 2026)
  13. OpenClaw 2026.10.2 release notes (docs)
  14. OpenClaw 2026.10.2 changelog
  15. OpenClaw release v2026.10.1 (GitHub, Oct 10, 2026)
  16. OpenClaw 2026.10.1 release notes (docs)
  17. OpenClaw 2026.10.1 changelog
  18. OpenClaw release v2026.8.1 (Aug 31, 2026)