OpenClaw 2026.2.1 – security hardening and Discord routing fixes

Security hardening (path traversal, LFI, exec injection), TLS 1.3 minimum, prompt guardrails, Discord thread routing and gateway timestamps, streaming stability, and memory search fixes—plus 20+ community PRs.

February 2, 2026

Original tweet: https://x.com/openclaw/status/2018293323199635545

Release highlights (2026.2.1)

  • Security hardening: path traversal, LFI, and exec injection fixes; prompt guardrails tightened.
  • Transport: TLS 1.3 minimum enforced.
  • Discord: thread routing fixes and gateway message timestamps.
  • Stability: streaming stability improvements; memory search fixes.
  • Community: 20+ community PRs merged—thank you.

Why it matters

Stronger defaults (TLS 1.3, input guardrails) reduce exposure; Discord reliability and streaming stability improve day-to-day agent runs; memory search fixes reduce retrieval flakiness.

Quick upgrade notes

  • Pull latest and rebuild/restart your gateway/agent stack.
  • Verify your TLS termination supports TLS 1.3; if you’re behind a proxy, ensure it negotiates 1.3 to upstream.
  • If you rely on Discord thread routing, re-check channel/thread mappings after upgrade.

Links

  • Release tweet: https://x.com/openclaw/status/2018293323199635545
  • Project: https://openclaw.ai
Share this post

Related Posts