Subs -10% SUB-10
Claws -25% LAUNCH-CLAWS
Six New OpenClaw Vulnerabilities Found by AI-Powered Code Scanner
$ ./blog/news
News

Six New OpenClaw Vulnerabilities Found by AI-Powered Code Scanner

ClawHosters
ClawHosters by Daniel Samer
3 min read

Endor Labs security researchers ran their AI-driven SAST tool against OpenClaw's codebase in early February and pulled out six vulnerabilities. Four rated high severity. All six had working proof-of-concept exploits within 24 hours of discovery.

Endor Labs published the full technical breakdown on February 5. Patches landed in v2026.2.14 between February 14 and 15.

What They Found

CVE / Advisory Severity Type
CVE-2026-26322 HIGH (7.6) Gateway Tool SSRF
CVE-2026-26319 HIGH (7.5) Telnyx Webhook Auth Bypass
GHSA-pg2v-8xwh-qhcc MODERATE (6.5) Urbit Auth SSRF
GHSA-56f2-hvwg-5743 HIGH (7.6) Image Tool SSRF
GHSA-c37p-4qqg-3p76 MODERATE (6.5) Twilio Webhook Bypass
CVE-2026-26329 HIGH (7.1) Path Traversal Upload

Three of the six are SSRF bugs. Those let an attacker reach internal services, cloud metadata endpoints, or anything else the server can talk to. The path traversal flaw (CVE-2026-26329) is different: an authenticated attacker could read arbitrary files through Playwright's upload handling.

The two webhook bypasses are worth paying attention to. Infosecurity Magazine reports that Telnyx webhooks used a fail-open pattern, meaning a missing or malformed signature would pass validation instead of blocking the request. Twilio's bypass worked through an ngrok loopback.

Root Causes

Same story across all six: missing input validation, fail-open auth defaults, and multi-layer data flows where nobody checked the intermediate steps. According to CSO Online's analysis, the AI SAST tool caught these because it could trace data across function boundaries that traditional static analysis would miss.

What You Should Do

If you're self-hosting OpenClaw, update to v2026.2.14 or later. The Image Tool SSRF was actually patched earlier in v2026.2.2, so if you're on anything older than mid-February builds, you're probably exposed to at least some of these.

If you're running on ClawHosters, we patched all instances within hours of each fix going live. Container isolation also limits the blast radius of SSRF attacks since each instance only sees its own network namespace.

For a broader look at hardening your OpenClaw setup, check out the security hardening guide. And if you want automated scanning, the safety scanner post covers that.

Frequently Asked Questions

Yes. All six were patched between February 2 and February 15, 2026. The main batch landed in v2026.2.14. Update your OpenClaw instance to that version or newer and you're covered.

It depends on your setup. If your OpenClaw instance can reach cloud metadata endpoints (like AWS 169.254.169.254), an SSRF could potentially grab IAM credentials or other secrets. Container isolation and network segmentation reduce that risk significantly.

ClawHosters applied all patches within hours of release. Each customer instance runs in its own isolated container with restricted network access, which limits what SSRF attacks can reach even before patching.
*Last updated: February 2026*

Sources

  1. 1 Endor Labs published the full technical breakdown
  2. 2 Infosecurity Magazine reports
  3. 3 CSO Online's analysis
  4. 4 ClawHosters
  5. 5 security hardening guide
  6. 6 safety scanner post