OpenClaw allows unauthenticated discovery TXT records to steer routing and TLS pinning
Summary
Discovery beacons (Bonjour/mDNS and DNS-SD) include TXT records such as lanHost, tailnetDns, gatewayPort, and gatewayTlsSha256. TXT records are unauthenticated.
Prior to the fix, 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.
Distribution / Exposure
The iOS and Android apps are currently 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.
CVSS can still be used for the technical (base) severity of the bug; limited distribution primarily affects environmental risk.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected:
<= 2026.2.13(latest published on npm as of 2026-02-14) - Patched: planned for
>= 2026.2.14(not yet published at time of writing)
Fix
- Clients now prefer the resolved service endpoint (SRV + A/AAAA) over TXT-provided routing hints.
- Discovery-provided fingerprints no longer override stored TLS pins.
- iOS/Android: first-time TLS pins require explicit user confirmation (fingerprint shown; no silent TOFU).
- iOS/Android: discovery-based direct connects are TLS-only.
- Android: hostname verification is no longer globally disabled (only bypassed when pinning).
Fix Commit(s)
- d583782ee322a6faa1fe87ae52455e0d349de586
Credits
Thanks @simecek for reporting.
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Paquete de npm | openclaw | < 2026.2.14 | 2026.2.14 |
Referencias
- https://github.com/openclaw/openclaw/security/advisories/GHSA-pv58-549p-qh99
- https://nvd.nist.gov/vuln/detail/CVE-2026-26327
- https://github.com/openclaw/openclaw/commit/d583782ee322a6faa1fe87ae52455e0d349de586
- https://github.com/openclaw/openclaw
- https://github.com/openclaw/openclaw/releases/tag/v2026.2.14
- Vector CVSS
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- Debilidad (CWE)
CWE-345- Plataforma
- npm
- Paquete
openclaw- Publicada
- 18.02.2026
- Actualizado
- 11.10.2026 10:22
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-pv58-549p-qh99 - CC BY 4.0
Historial de vulnerabilidades: openclaw
Todas las vulnerabilidades publicadas de este paquete (Paquete de npm), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
- Entradas en total
- 589
- Primera → última
- 02.2026 10.2026
- Sin corrección
- 9
- Explotada en ataques
- 0
Distribución por gravedad
- Crítica 20
- Alta 215
- Media 300
- Baja 54
Divulgaciones por año
- 2026: 589
-
OpenClaw allows unauthenticated discovery TXT records to steer routing and TLS pinning esta entrada
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.