Loading story…
OpenClaw disclosed two high-severity vulnerabilities affecting versions before 2026.2.21 and 2026.3.25, exposing gateway routes to unauthorized access and privilege escalation. CVE-2026-32045 is an authentication bypass in HTTP gateway routes caused by incorrect application of tokenless Tailscale header authentication, allowing attackers on trusted networks to reach protected routes without valid tokens or passwords. The issue is tracked as CWE-290 and carries a CVSS v3.1 vector of AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N, indicating a confidentiality-focused impact.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
6 events from the most recent confirmed update back to the earliest known activity.
A high-severity OpenClaw vulnerability, CVE-2026-35663, was publicly disclosed affecting versions before 2026.3.25. The privilege escalation flaw in the backend reconnect process allowed non-admin operators to self-request broader scopes, bypass pairing requirements, and reconnect as operator.admin.
CVE-2026-35669 was publicly disclosed on April 10, 2026 as a high-severity OpenClaw privilege escalation vulnerability. It was classified as CWE-648 and described as allowing a low-privileged attacker to obtain operator.admin runtime scope and perform unauthorized actions.
The privilege escalation vulnerability later assigned CVE-2026-35669 was received by disclosure@vulncheck.com on April 10, 2026. The flaw involved improper authentication scope handling in OpenClaw plugin HTTP routes.
OpenClaw addressed CVE-2026-35669 in version 2026.3.25, fixing a privilege escalation flaw in gateway-authenticated plugin HTTP routes that incorrectly minted the operator.admin runtime scope. The bug affected versions before 2026.3.25 and could let low-privileged users gain elevated administrative capabilities.
A high-severity vulnerability, CVE-2026-32045, was disclosed for OpenClaw on March 21, 2026. The issue was classified as CWE-290 and described as enabling unauthorized access to HTTP gateway routes without valid authentication credentials.
OpenClaw addressed CVE-2026-32045 in version 2026.2.21, fixing an authentication bypass in HTTP gateway routes caused by incorrect application of tokenless Tailscale header authentication. The flaw affected versions prior to 2026.2.21 and could allow attackers on trusted networks to access routes without valid tokens or passwords.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
3 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcecvefeed.io
Open sourcecvefeed.io
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Two high-severity vulnerabilities in OpenClaw exposed paths for authenticated users to gain access beyond their intended roles. **CVE-2026-32042** affects versions before `2026.2.25` and allows an attacker with valid shared gateway authentication to present a self-signed, unpaired device identity and bypass pairing requirements, then self-assign elevated operator scopes including `operator.admin`. The issue is classified as `CWE-863` and effectively turns a trusted but unapproved device identity into a route for privilege escalation. A second flaw, **CVE-2026-32051**, affects OpenClaw versions before `2026.3.1` and allows users with `operator.write` scope to reach owner-only tool surfaces such as gateway and cron through agent runs in scoped-token deployments. The authorization mismatch lets lower-privileged authenticated users perform control-plane actions that should be restricted to owners, creating high risk to confidentiality, integrity, and availability. Advisories for both issues point to fixes and security guidance through GitHub and VulnCheck.
Jun 29, 2026
OpenClaw disclosed several high-severity vulnerabilities affecting multiple releases, including authorization bypass in QQBot pre-dispatch slash commands, privilege escalation in the trusted-proxy Control UI WebSocket, and node authority expansion through pairing reconnection logic. The QQBot issue, tracked as **`CVE-2026-53834`** and mirrored in GitHub advisory **`GHSA-77pv-3w4q-vrj5`**, affects versions up to **`2026.4.26`** and allows senders to trigger slash-command handling before `allowFrom` policy checks are enforced. The vendor said the flaw is limited to the QQBot feature and its configuration, with the first stable fix released in **`2026.4.27`**.
Jun 29, 2026
OpenClaw disclosed two high-severity server-side request forgery vulnerabilities affecting versions prior to `2026.3.1` and `2026.3.28`. **CVE-2026-32902** impacts `web_search` citation redirect resolution, where attacker-influenced redirect targets can cause the OpenClaw gateway host to send requests to private-network destinations. The issue is tracked as `CWE-918` and was assigned a CVSS v3.1 vector of `AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L`, indicating remote exploitation without privileges or user interaction.
Jun 29, 2026