Before OpenClaw 2026.4.2, Android accepted non-loopback cleartext ws:// gateway endpoints and would send stored gateway credentials over that connection. Discovery beacons or setup codes could therefore steer the client onto a cleartext remote endpoint.
A user who followed a forged discovery result or scanned a crafted setup code could disclose stored gateway credentials to an attacker-controlled endpoint in plaintext. This was a transport-security bug in the Android gateway client.
openclaw (npm)<= 2026.4.1>= 2026.4.22026.4.1a941a4fef9bc43b2973c92d0dcff5b8a426210c5 — require TLS for remote Android gateway endpointsThe fix is present on main and is staged for OpenClaw 2026.4.2. Publish this advisory after the 2026.4.2 npm release is live.
Thanks @zsxsoft for reporting.
{
"cwe_ids": [
"CWE-200"
],
"github_reviewed_at": "2026-04-07T18:16:06Z",
"nvd_published_at": null,
"severity": "MODERATE",
"github_reviewed": true
}