# CVE-2026-26327: OpenClaw allows unauthenticated discovery TXT records to steer routing and TLS pinning > Attackers on shared LANs can spoof discovery records to redirect clients and bypass TLS pinning, potentially stealing credentials. - **Severity:** High 7.1 (`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`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 19 Feb 2026 - **Updated:** 20 Feb 2026 - **Also known as:** GHSA-pv58-549p-qh99 ## What is CVE-2026-26327? CVE-2026-26327 is a high-severity vulnerability in Openclaw Openclaw, published on 19 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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). Weakness: CWE-345 (Insufficient Verification of Data Authenticity) ## Which versions are affected by CVE-2026-26327? 2 open source packages ship an affected version, including openclaw. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `openclaw` | npm | All versions | 2026.2.14 | | `openclaw` | npm | All versions | 2026.2.14 | Products: Openclaw Openclaw. ## How do I fix CVE-2026-26327? Upgrade openclaw to 2026.2.14 or later. ## Is CVE-2026-26327 being exploited? There is no known exploitation of CVE-2026-26327 in the wild and no public exploit code. ## Other vulnerabilities in Openclaw Openclaw - [CVE-2026-28363](https://insights.sbomify.com/CVE-2026-28363/): Security feature bypass in OpenClaw (critical 9.9) - [CVE-2026-30741](https://insights.sbomify.com/CVE-2026-30741/): Code injection in n/a (critical 9.8) - [CVE-2026-33579](https://insights.sbomify.com/CVE-2026-33579/): OpenClaw < 2026.3.28 - Privilege Escalation via Missing Caller Scope Validation in Device Pair Approval (critical 9.4) - [CVE-2026-32922](https://insights.sbomify.com/CVE-2026-32922/): OpenClaw < 2026.3.11 - Privilege Escalation via Unvalidated Scope in device.token.rotate (critical 9.4) - [CVE-2026-32978](https://insights.sbomify.com/CVE-2026-32978/): OpenClaw < 2026.3.11 - Approval Bypass via Unrecognized Script Runners (critical 9.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-26327 and fix it if it is affected. What it is: CVE-2026-26327 is a high-severity vulnerability in Openclaw Openclaw, published on 19 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-26327 in the wild and no public exploit code. Affected packages and fixed versions: - openclaw (npm): affected all versions; fixed in 2026.2.14 - openclaw (npm): affected all versions; fixed in 2026.2.14 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-26327/ (Markdown: https://insights.sbomify.com/CVE-2026-26327/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26327 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26327 - OSV: https://osv.dev/vulnerability/CVE-2026-26327 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-26327/ Summaries are generated and may contain mistakes; the official description above is the record.