CVE-2026-26327: Openclaw OpenClaw Allows Unauthenticated Discovery TXT Vulnerability

HIGH
Advisory Identifier: GHSA-pv58-549p-qh99
CWE-345
Published
Advisory Summary

CVE-2026-26327 is a HIGH openclaw allows unauthenticated discovery txt vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting Openclaw libraries in the npm ecosystem. The issue involves openclaw allows unauthenticated discovery txt records to steer routing and tls pinning. Remediation is available by upgrading affected packages to version 2026.2.14.

CVE-2026-26327 at a Glance

CVE Identifier CVE-2026-26327
GHSA Identifier GHSA-pv58-549p-qh99
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-345: Insufficient Verification of Data Authenticity
Affected Product Openclaw
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-26327

To remediate this vulnerability, upgrade all affected Openclaw dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

openclaw fixed: 2026.2.14
npm install openclaw@2026.2.14
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls openclaw

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-26327, inspect your project dependencies using npm:

npm ls openclaw

Analyze the terminal output to locate any version of Openclaw in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2026.2.14), your application is affected.

Note: The npm ls openclaw command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. In Openclaw, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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.

CVE-2026-26327 Affected Openclaw Versions

1 component(s)
Fixed Versions:
2026.2.14
Product / Package Ecosystem Affected Versions Fixed Version
openclaw
npm
< 2026.2.14
2026.2.14

References

Frequently Asked Questions

What is CVE-2026-26327?
CVE-2026-26327 is a security vulnerability in Openclaw involving OpenClaw allows unauthenticated discovery TXT records to steer routing and TLS pinning under CWE-345: Insufficient Verification of Data Authenticity.
Which Openclaw versions are affected?
Affected versions include releases prior to 2026.2.14 across affected packages: openclaw.
What version fixes CVE-2026-26327?
Upgrading to 2026.2.14 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openclaw affected?
Yes, openclaw is affected in releases prior to 2026.2.14. Upgrade your dependency to 2026.2.14 or later.
What CWE is associated with CVE-2026-26327?
CVE-2026-26327 is classified under CWE-345: Insufficient Verification of Data Authenticity (The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.).
How can I check npm dependencies for CVE-2026-26327?
Run the dependency tree command: 'npm ls openclaw'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-pv58-549p-qh99",
  "modified" : "2026-02-20T16:45:30Z",
  "published" : "2026-02-18T00:33:35Z",
  "aliases" : [ "CVE-2026-26327" ],
  "summary" : "OpenClaw allows unauthenticated discovery TXT records to steer routing and TLS pinning",
  "details" : "## Summary\n\nDiscovery beacons (Bonjour/mDNS and DNS-SD) include TXT records such as `lanHost`, `tailnetDns`, `gatewayPort`, and `gatewayTlsSha256`. TXT records are unauthenticated.\n\nPrior to the fix, some clients treated TXT values as authoritative routing/pinning inputs:\n\n- iOS and macOS: used TXT-provided host hints (`lanHost`/`tailnetDns`) and ports (`gatewayPort`) to build the connection URL.\n- iOS and Android: allowed the discovery-provided TLS fingerprint (`gatewayTlsSha256`) to override a previously stored TLS pin.\n\nOn 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.\n\n## Distribution / Exposure\n\nThe 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.\n\nCVSS can still be used for the technical (base) severity of the bug; limited distribution primarily affects environmental risk.\n\n## Affected Packages / Versions\n\n- Package: `openclaw` (npm)\n- Affected: `<= 2026.2.13` (latest published on npm as of 2026-02-14)\n- Patched: planned for `>= 2026.2.14` (not yet published at time of writing)\n\n## Fix\n\n- Clients now prefer the resolved service endpoint (SRV + A/AAAA) over TXT-provided routing hints.\n- Discovery-provided fingerprints no longer override stored TLS pins.\n- iOS/Android: first-time TLS pins require explicit user confirmation (fingerprint shown; no silent TOFU).\n- iOS/Android: discovery-based direct connects are TLS-only.\n- Android: hostname verification is no longer globally disabled (only bypassed when pinning).\n\n## Fix Commit(s)\n\n- d583782ee322a6faa1fe87ae52455e0d349de586\n\n## Credits\n\nThanks @simecek for reporting.",
  "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "openclaw"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2026.2.14"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "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" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/commit/d583782ee322a6faa1fe87ae52455e0d349de586"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/openclaw/openclaw"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/releases/tag/v2026.2.14"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-345" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-18T00:33:35Z",
    "nvd_published_at" : "2026-02-19T23:16:26Z"
  }
}