Loading story…
High-severity vulnerabilities were disclosed in OpenClaw and CTEK Chargeportal, with both flaws tied to insecure WebSocket handling that can let attackers gain unauthorized control. In CVE-2026-22172, OpenClaw versions prior to 2026.3.12 fail to properly bind authorized scopes in shared-token or password-authenticated WebSocket sessions, allowing a low-privileged user to self-assign elevated permissions such as operator.admin and perform admin-only gateway operations. The issue is classified as CWE-862 and carries a CVSS v3.1 score reflecting high impact to confidentiality, integrity, and availability.
In CVE-2026-25192, CTEK Chargeportal exposes WebSocket endpoints that do not properly authenticate critical functions, enabling an unauthenticated attacker to impersonate EV charging stations by using a known or discovered station identifier. That access can be used to send or receive OCPP commands as a legitimate charger, potentially leading to unauthorized control of charging infrastructure, privilege escalation, and corruption of backend charging data. The flaw is tracked as CWE-306 and is covered in CISA advisory ICSA-26-078-06, with impact rated high for confidentiality and integrity.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
A high-severity missing-authentication vulnerability in CTEK Chargeportal was disclosed as CVE-2026-25192. The issue allows unauthenticated attackers to impersonate charging stations over OCPP WebSocket endpoints using a known or discovered station identifier and manipulate charging infrastructure traffic.
A high-severity authorization bypass in OpenClaw versions prior to 2026.3.12 was disclosed as CVE-2026-22172. The flaw allows low-privileged shared-token or password-authenticated users to self-assign elevated scopes such as operator.admin through improperly bound WebSocket authorization scopes.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
cvereports.com
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
A high-severity flaw in **OpenClaw** (also known as *Clawdbot* / *Moltbot*) enables **one-click remote code execution (RCE)** by abusing how the Control UI auto-connects to a gateway specified via a crafted URL. The issue is tracked as **CVE-2026-25253** (CVSS **8.8**) and was fixed in **OpenClaw 2026.1.29**; the core weakness is that the UI trusts `gatewayUrl` from the query string and sends a stored gateway token in the WebSocket connection payload, allowing **token exfiltration** to an attacker-controlled server. With the stolen token, an attacker can connect to the victim’s local gateway and perform privileged actions—such as modifying configuration (e.g., sandbox/tool policies) and invoking privileged operations—resulting in **full gateway compromise** and RCE. Separate reporting also highlights architectural risk in OpenClaw’s local WebSocket-based Chrome orchestration, noting that (prior to patching) unauthenticated connections could be initiated from JavaScript running in a user’s browser, enabling cross-tab/session credential theft; users are advised to **patch immediately** and be cautious about deployment given ongoing security concerns.
Jun 29, 2026
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.
Jun 29, 2026