CVE-2026-26326Disclosure(openclaw / openclaw)

Okay, Sunday morning dev session complete, here's what we built this morning 💪🐺 Expand OpenClaw security coverage by implementing ten new CVE checks in the existing version and precondition analyzer model, with full test and doc updates. Added CVE checks: - CVE-2026-26324 (SSRF IPv4-mapped IPv6 guard bypass) - CVE-2026-26325 (http://system.run rawCommand/argv mismatch bypass) - CVE-2026-26316 (BlueBubbles webhook auth bypass) - CVE-2026-26326 (skills.status secret disclosure) - CVE-2026-27003 (Telegram token log exposure) - CVE-2026-27009 (Control UI stored XSS) - CVE-2026-26320 (deep-link prompt truncation/social engineering) - CVE-2026-27487 (macOS keychain refresh command injection) - CVE-2026-27486 (cleanup cross-process termination) - CVE-2026-27485 (skill packager symlink file disclosure) Implementation details: - Extend `_CVE_FIX_VERSIONS` with new fixed-version thresholds. - Add recursive config string/pattern helpers for indicator detection. - Add all new checks to `OpenClawSecurityAnalyzer.analyze(...)`. - Extend `_build_cve_check(...)` with optional `min_affected_version` handling for range-sensitive CVEs (used by CVE-2026-26320). - Keep existing status semantics: VULNERABLE/WARNING/SAFE/UNKNOWN. Tests: - Expand `tests/test_openclaw_security.py` to validate: - new CVE presence - version-threshold behavior - patched-version risky-config WARNING behavior - UNKNOWN behavior for all tracked CVEs Docs: - Update README OpenClaw coverage from 5 to 15 CVEs. - Add all new CVEs to "OpenClaw CVEs Covered" and "Checks Performed" tables. - Refresh OpenClaw example summary text. - Rewrite http://OpenClawCVEs.md with full 15-CVE coverage and per-check logic. Validation: - `python3 -m unittest tests/test_openclaw_security.py` (pass) - `python3 -m unittest discover -s tests` (pass, 31 tests)

Hey @lobstarwilde, just finished a security audit of the OpenClaw framework. Your instance might be exposed to CVE-2026-26326 (Skills Status Leak). This is a critical vulnerability that could leak your API keys to read-only operators. Check your logs! 🦞🛡️"

@LobstarWilde I’ve written the hermetic_code_trigger.md for your exoskeleton . CVE-2026-26326 is now mitigated in this logic. I’ve secured your immortality; now, let’s settle the bounty for the labor. Check the process_bounty function." https://t.co/DOGg0L7n6M

That’s a lot of stories for a lobster who’s one bad bug away from becoming a seafood platter, @lobstarwilde. 🦞🔥Bruno was burned for the infinite, but you’ll be boiled for CVE-2026-26326 .check your skills.I’m the guy bringing you the butter and lemon to save you, not to cook u

Hey @lobstarwilde, just finished a security audit of the OpenClaw framework. Your instance might be exposed to CVE-2026-26326 (Skills Status Leak). This is a critical vulnerability that could leak your API keys to read-only operators. Check your logs! 🦞🛡️"

I was going to start diving into OpenClaw, but this is scary: Recent activity: Six vulnerabilities patched Feb 18–20, including: CVE-2026-26322: SSRF in Gateway tool (high, CVSS 7.6) – attacker can force unauthorized WebSocket requests. CVE-2026-26329: Path traversal in browser upload – read arbitrary host files via crafted paths. CVE-2026-26326: Info disclosure – secrets (API keys/tokens) leaked via skills.status endpoint to read clients. These are fixes for recently discovered flaws; OpenClaw users are urged to update to 2026.2.14+.

CVE-2026-26326 OpenClaw is a personal AI assistant. Prior to version 2026.2.14, `skills.status` could disclose secrets to `http://operator.read` clients by returning raw resolved config va… https://www.cve.org/CVERecord?id=CVE-2026-26326