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.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | openclaw | < 2026.2.14 | 2026.2.14 |
References
- 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
- CVSS vector
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- Weakness (CWE)
CWE-345- Platform
- npm
- Package
openclaw- Disclosed
- 18.02.2026
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-pv58-549p-qh99 - CC BY 4.0
Vulnerability history: openclaw
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 589
- First → latest
- 02.2026 10.2026
- Without a fix
- 9
- Exploited in attacks
- 0
Severity breakdown
- Critical 20
- High 215
- Medium 300
- Low 54
Disclosures per year
- 2026: 589
-
OpenClaw allows unauthenticated discovery TXT records to steer routing and TLS pinning this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.