{"id":"CVE-2026-26327","summary":"OpenClaw allows unauthenticated discovery TXT records to steer routing and TLS pinning","details":"OpenClaw is a personal AI assistant. Discovery beacons (Bonjour/mDNS and DNS-SD) include TXT records such as `lanHost`, `tailnetDns`, `gatewayPort`, and `gatewayTlsSha256`. TXT records are unauthenticated. Prior to version 2026.2.14, some clients treated TXT values as authoritative routing/pinning inputs. iOS and macOS used TXT-provided host hints (`lanHost`/`tailnetDns`) and ports (`gatewayPort`) to build the connection URL. iOS and Android allowed the discovery-provided TLS fingerprint (`gatewayTlsSha256`) to override a previously stored TLS pin. On a shared/untrusted LAN, an attacker could advertise a rogue `_openclaw-gw._tcp` service. This could cause a client to connect to an attacker-controlled endpoint and/or accept an attacker certificate, potentially exfiltrating Gateway credentials (`auth.token` / `auth.password`) during connection. As of time of publication, the iOS and Android apps are alpha/not broadly shipped (no public App Store / Play Store release). Practical impact is primarily limited to developers/testers running those builds, plus any other shipped clients relying on discovery on a shared/untrusted LAN. Version 2026.2.14 fixes the issue. Clients now prefer the resolved service endpoint (SRV + A/AAAA) over TXT-provided routing hints. Discovery-provided fingerprints no longer override stored TLS pins. In iOS/Android, first-time TLS pins require explicit user confirmation (fingerprint shown; no silent TOFU) and discovery-based direct connects are TLS-only. In Android, hostname verification is no longer globally disabled (only bypassed when pinning).","aliases":["GHSA-pv58-549p-qh99"],"modified":"2026-08-12T03:51:09.394868244Z","published":"2026-02-19T22:59:36.376Z","database_specific":{"cwe_ids":["CWE-345"],"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/26xxx/CVE-2026-26327.json","cna_assigner":"GitHub_M"},"references":[{"type":"WEB","url":"https://github.com/openclaw/openclaw/releases/tag/v2026.2.14"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/26xxx/CVE-2026-26327.json"},{"type":"ADVISORY","url":"https://github.com/openclaw/openclaw/security/advisories/GHSA-pv58-549p-qh99"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-26327"},{"type":"FIX","url":"https://github.com/openclaw/openclaw/commit/d583782ee322a6faa1fe87ae52455e0d349de586"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://github.com/openclaw/openclaw","events":[{"introduced":"0"},{"fixed":"b5ab92eef4e4f6099c98817e0917c99ec9e03045"},{"fixed":"d583782ee322a6faa1fe87ae52455e0d349de586"}],"database_specific":{"cpe":"cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:node.js:*:*","extracted_events":[{"introduced":"0"},{"fixed":"2026.2.14"}],"source":["CPE_RANGE","REFERENCES"]}}],"versions":["v2026.2.13","v2026.2.12","v2026.2.9","v2026.2.6-3","v2026.2.6-2","v2026.2.6-1","v2026.2.6","v2026.2.3","v2026.2.2","v2026.2.1","v2026.1.30","v2026.1.29","v2026.1.24-1","v2026.1.24","v2026.1.23","v2026.1.22","v2026.1.21","v2026.1.20","v2026.1.16-2","v2026.1.15","v2026.1.14-1","v2026.1.13","v2026.1.12-2","v2026.1.12","v2026.1.11-3","v2026.1.11-2","v2026.1.11-1","v2026.1.11","v2026.1.10","v2026.1.9","v2026.1.8","v2026.1.5-3","v2026.1.5-2","v2026.1.5-1","v2026.1.5","v2.0.0-beta5","v2.0.0-beta4","v2.0.0-beta3","v2.0.0-beta2","v2.0.0-beta1","v1.3.0","v1.2.2","v1.2.1","v1.2.0","v1.1.0","v1.0.4","v0.1.3","v0.1.2","v0.1.1","v0.1.0"],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-26327.json"}}],"schema_version":"1.9.0","severity":[{"type":"CVSS_V4","score":"CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"}]}