CVE-2026-42566

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Meshtastic is an open source mesh networking solution. Prior to version 2.7.23.b246bcd, a single node advertising a User.long_name that contains a malformed character encoding can render other radios unusable over BLE when managed through the iOS app. The malformed name does not need to be maliciously crafted — it can arise from ordinary buffer truncation and has been observed occurring naturally in the wild. At least one code path could place a null terminator in the middle of a multibyte sequence, leaving a malformed User.long_name in the node database. The problem surfaced downstream: the iOS app enforced encoding validation and therefore cannot parse a node database once it contains a poisoned entry. This caused BLE sync to enter a fail/retry loop, resulting in loss of control over the affected device. For a typical user managing their radio with the iOS app, the device becomes effectively unusable until the poisoned node ages out of the on-device database, or unless they have an alternate management path (e.g., the Python CLI, which can be used to identify and remove the offending entries manually). Because the malformed name propagates through the mesh, the temporary presence of a single affected node can degrade BLE management for iOS users across a wide geographical area for an extended period. Less technical users have no straightforward recovery path. Starting in version 2.7.23.b246bcd, the firmware has added input sanitization and regression tests demonstrating recovery for already-poisoned devices. The apps have also taken steps to ensure more graceful handling of malformed encoding sequences as well.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

July 19, 2026

Last Modified

August 18, 2026

Advisory Details (2)

Auto-updated Jul 19, 2026
Fix referenced — no release confirmed yet. Sources: github, github_commit.
GitHub commit

commit 2cc13a1132d9 (meshtastic/firmware)

Fix landed in meshtastic/firmware commit 2cc13a1132d9 — awaiting tagged release

https://github.com/meshtastic/firmware/commit/2cc13a1132d94b66a9505e7f07ee2d3e83bd0c95
GitHub advisoryMentions a patch (unverified)

Malformed encoding in User.long_name broadcast over LoRa causes client decode failure · Advisory · meshtastic/firmware · GitHub

https://github.com/meshtastic/firmware/security/advisories/GHSA-7ph5-2mjv-69h8

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 33× 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.

Showing the most recent 100 of 132 refreshes on record for this CVE.

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. None are among the latest 100 rows. The 32 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  3. 2026-10-12 16:07 UTCEG score recompute
  4. 2026-10-11 19:49 UTCEG score recompute
  5. 2026-10-11 17:03 UTCEG score recompute
  6. 2026-10-11 14:29 UTCEG score recompute
  7. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-10-04 14:58 UTCEG score recompute
  16. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-10-01 07:55 UTCEG score recompute
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  20. 2026-09-28 06:28 UTCEG score recompute
  21. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  22. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  23. 2026-09-24 03:31 UTCEG score recompute
  24. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-09-23 01:47 UTCEG score recompute
Show 75 more
  1. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-09-18 04:06 UTCEG score recompute
  4. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-09-17 05:16 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-09-16 12:50 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-09-14 04:30 UTCEG score recompute
  10. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-09-13 03:22 UTCEG score recompute
  12. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-09-12 01:05 UTCEG score recompute
  14. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-09-11 09:38 UTCEG score recompute
  16. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-09-09 12:22 UTCEG score recompute
  19. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-09-07 23:03 UTCEG score recompute
  21. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-09-05 22:10 UTCEG score recompute
  24. 2026-09-05 09:43 UTCEG score recompute
  25. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  26. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  27. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  28. 2026-08-31 04:00 UTCEG score recompute
  29. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  30. 2026-08-30 02:42 UTCEG score recompute
  31. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  32. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  33. 2026-08-28 01:41 UTCEG score recompute
  34. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  35. 2026-08-26 22:12 UTCEG score recompute
  36. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  37. 2026-08-25 20:16 UTCEG score recompute
  38. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  39. 2026-08-24 19:01 UTCEG score recompute
  40. 2026-08-23 01:33 UTCEG score recompute
  41. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  42. 2026-08-22 00:41 UTCEG score recompute
  43. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  44. 2026-08-20 23:47 UTCEG score recompute
  45. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  46. 2026-08-19 22:55 UTCEG score recompute
  47. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  48. 2026-08-18 18:25 UTCEG score recompute
  49. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  50. 2026-08-17 21:05 UTCEG score recompute
  51. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  52. 2026-08-16 17:48 UTCEG score recompute
  53. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  54. 2026-08-16 05:20 UTCEG score recompute
  55. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  56. 2026-08-15 04:29 UTCEG score recompute
  57. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  58. 2026-08-14 03:36 UTCEG score recompute
  59. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  60. 2026-08-12 14:18 UTCEG score recompute
  61. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  62. 2026-08-12 01:52 UTCEG score recompute
  63. 2026-08-11 13:43 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  64. 2026-08-11 00:55 UTCEG score recompute
  65. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  66. 2026-08-09 23:53 UTCEG score recompute
  67. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  68. 2026-08-08 23:01 UTCEG score recompute
  69. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  70. 2026-08-07 22:08 UTCEG score recompute
  71. 2026-08-06 21:16 UTCEG score recompute
  72. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  73. 2026-08-05 20:24 UTCEG score recompute
  74. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  75. 2026-08-04 19:31 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-42566?
CVE-2026-42566 is a high-severity vulnerability; its CVE record was published on July 19, 2026. Meshtastic is an open source mesh networking solution. Prior to version 2.7.23.b246bcd, a single node advertising a User.longname that contains a malformed character encoding can render other radios unusable over BLE when managed through the iOS app. The malformed name does not need to be…
When was the CVE record for CVE-2026-42566 published?
The CVE record for CVE-2026-42566 was published on July 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 August 18, 2026; the record at its source may have been updated since.
Is CVE-2026-42566 actively exploited?
CVE-2026-42566 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42566?
CVE-2026-42566 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-42566?
A fix for CVE-2026-42566 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-42566

Explore →

Is Your Infrastructure Affected by CVE-2026-42566?

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

Book a Demo →Browse All CVEs