CVE-2026-26327

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.1% (1st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-8420 (ENISA EUVD) · GHSA-pv58-549p-qh99 (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

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 advisoryMentions a patch (unverified)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmopenclaw @ 2026.2.14 (fixes < 2026.2.14)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
openclaw—
  • every version up to 2026.2.14: fixed in 2026.2.14
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 96 are merged into the row they repeat.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-11-01 07:56 UTCGHSA enrichmentGHSA-pv58-549p-qh99 · GitHub severity HIGH
  3. 2026-11-01 07:56 UTCEG score recompute
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-10-31 00:55 UTCOSV refresh
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-25 14:39 UTCEG score recompute
  12. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-23 04:27 UTCEG score recompute
  15. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-18 03:51 UTCEG score recompute
  21. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  24. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  25. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
Show 68 more
  1. 2026-10-12 16:18 UTCEG score recompute
  2. 2026-10-11 20:00 UTCEG score recompute
  3. 2026-10-11 17:13 UTCEG score recompute
  4. 2026-10-11 14:45 UTCEG score recompute
  5. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  6. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-10-08 14:35 UTCOSV refresh
  10. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-09-18 20:20 UTCOSV refresh
  22. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  24. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  25. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  26. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  27. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  28. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  29. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  30. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  31. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  32. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  33. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  34. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  35. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  36. 2026-08-30 23:23 UTCOSV refresh
  37. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  38. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  39. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  40. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  41. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  42. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  43. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  44. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  45. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  46. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  47. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  48. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  49. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  50. 2026-08-14 09:31 UTCEG score recompute
  51. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  52. 2026-08-12 01:58 UTCEG score recompute
  53. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  54. 2026-08-09 09:07 UTCEG score recompute
  55. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  56. 2026-08-07 21:21 UTCEG score recompute
  57. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  58. 2026-08-06 03:24 UTCEG score recompute
  59. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  60. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  61. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  62. 2026-08-02 20:04 UTCEG score recompute
  63. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  64. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  65. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  66. 2026-07-28 15:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  67. 2026-07-27 14:13 UTCEG score recomputeFirst assessed: 6.5 MEDIUM
  68. 2026-07-27 13:55 UTCOSV refresh

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-26327?
CVE-2026-26327 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-26327 published?
The CVE record for CVE-2026-26327 was published on February 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-26327 actively exploited?
CVE-2026-26327 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-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?
A fix for CVE-2026-26327 is available: update to the fixed version the vendor names in its advisory.

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.

Book a Demo →Browse All CVEs