CVE-2026-26327

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

February 19, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
Patch available. Sources: github_release, github, github_commit.
github Patch Available

Unauthenticated discovery TXT records could steer routing and TLS pinning · Advisory · openclaw/openclaw · GitHub

https://github.com/openclaw/openclaw/security/advisories/GHSA-pv58-549p-qh99
github_release Patch Available

openclaw 2026.2.14

Patch available: openclaw/openclaw v2026.2.14

https://github.com/openclaw/openclaw/releases/tag/v2026.2.14
github_commit

commit d583782ee322 (openclaw/openclaw)

Fix landed in openclaw/openclaw commit d583782ee322 — awaiting tagged release

https://github.com/openclaw/openclaw/commit/d583782ee322a6faa1fe87ae52455e0d349de586

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
openclaw—2026.2.14—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 20:20 UTCOSV refresh
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-17 19:30 UTCEPSS rescore
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-12 15:01 UTCEPSS rescore
  9. 2026-09-11 14:52 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-04 05:06 UTCEPSS rescore
  16. 2026-09-02 14:11 UTCEPSS rescore
  17. 2026-09-01 13:53 UTCEPSS rescore
  18. 2026-08-30 23:23 UTCOSV refresh
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:48 UTCEPSS rescore
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-21 23:49 UTCEPSS rescore
Show 25 more
  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-19 17:03 UTCEPSS rescore
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 09:31 UTCEG score recompute
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-12 01:58 UTCEG score recompute
  10. 2026-08-11 00:00 UTCEPSS rescore
  11. 2026-08-09 09:07 UTCEG score recompute
  12. 2026-08-08 16:37 UTCEPSS rescore
  13. 2026-08-07 21:21 UTCEG score recompute
  14. 2026-08-06 13:46 UTCEPSS rescore
  15. 2026-08-06 03:24 UTCEG score recompute
  16. 2026-08-05 19:17 UTCEPSS rescore
  17. 2026-08-04 15:10 UTCEPSS rescore
  18. 2026-08-03 10:36 UTCEPSS rescore
  19. 2026-08-02 20:04 UTCEG score recompute
  20. 2026-08-01 04:16 UTCEPSS rescore
  21. 2026-07-30 16:27 UTCEPSS rescore
  22. 2026-07-30 01:30 UTCEPSS rescore
  23. 2026-07-28 15:36 UTCEPSS rescore
  24. 2026-07-27 14:13 UTCEG score recompute
  25. 2026-07-27 13:55 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-26327?
CVE-2026-26327 is a medium vulnerability published on February 19, 2026. 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.…
When was CVE-2026-26327 disclosed?
CVE-2026-26327 was first published in the National Vulnerability Database on February 19, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-26327 actively exploited?
CVE-2026-26327 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.8% of all scored CVEs.
What is the CVSS score of CVE-2026-26327?
CVE-2026-26327 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-26327?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-26327, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-26327

Explore →

Is Your Infrastructure Affected by CVE-2026-26327?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs