CVE-2026-55732

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th 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
8.7EG
EchelonGraph verdictPlan a fixRemediate 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: 8.7Exploit: None knownExposed services: Not assessed

Upgrade to firmware version 8.4.20 (from the CVE record's solution, Switzerland National Cyber Security Centre (NCSC)) — apply it.

Out-of-bounds Read (CWE-125) in BACnet packet parsing (bacdt_datetime_to_tod) in Loytec LIP-ME201C, L-INX, L-GATE, L-ROC, L-IOB, L-DALI, L-VIS and L-PAD through 8.4.18 on LINX-A64 allows an unauthenticated remote attacker to crash linx_a64.exe and ultimately reboot the device via a malformed BACnet TimeSynchronization or UTC-TimeSynchronization packet with an invalid month value. The same vulnerability affects multiple other Loytec products.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
54
EG Risk 54/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)
Severity87% × 45%
The EG Score, 8.7 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: Upgrade to firmware version 8.4.20 (from the CVE record's solution, Switzerland National Cyber Security Centre (NCSC)). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

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

Upgrade to firmware version 8.4.20 (from the CVE record's solution, Switzerland National Cyber Security Centre (NCSC)). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

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 24, 2026

Last Modified

July 27, 2026

Advisory Details (1)

Auto-updated Jul 24, 2026
Fix named in the CVE record's solution (Switzerland National Cyber Security Centre (NCSC)).
Web page

DIBT-CVE-20260608-0001 BACnet crash due to invalid timesync message (HIGH)

https://www.loytec.com/support/product-security/advisories/8532-dibt-cve-20260608-0001-bacnet-crash-due-to-invalid-timesync-message-high

Vendor Advisories for CVE-2026-55732(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 57× 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 228 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 128 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% · 44th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  3. 2026-10-12 15:55 UTCEG score recompute
  4. 2026-10-11 19:38 UTCEG score recompute
  5. 2026-10-11 16:53 UTCEG score recompute
  6. 2026-10-11 14:16 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-04 07:46 UTCEG score recompute
  16. 2026-10-04 07:46 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-10-03 03:21 UTCEG score recompute
  19. 2026-10-03 03:21 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  20. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-10-01 06:09 UTCEG score recompute
  23. 2026-10-01 06:09 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  24. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
Show 75 more
  1. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-09-28 04:41 UTCEG score recompute
  3. 2026-09-28 04:40 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  4. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-09-25 10:14 UTCEG score recompute
  7. 2026-09-25 10:14 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  8. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-09-24 01:05 UTCEG score recompute
  10. 2026-09-24 01:05 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  11. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  12. 2026-09-23 11:15 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  13. 2026-09-22 22:36 UTCEG score recompute
  14. 2026-09-22 22:36 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  15. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  16. 2026-09-20 01:43 UTCEG score recompute
  17. 2026-09-20 01:43 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  18. 2026-09-18 22:29 UTCEG score recompute
  19. 2026-09-18 22:29 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  20. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  21. 2026-09-18 03:02 UTCEG score recompute
  22. 2026-09-18 03:02 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  23. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  24. 2026-09-17 01:59 UTCEG score recompute
  25. 2026-09-17 01:59 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  26. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  27. 2026-09-16 06:43 UTCEG score recompute
  28. 2026-09-16 06:43 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  29. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  30. 2026-09-15 09:40 UTCEG score recompute
  31. 2026-09-15 09:40 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  32. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  33. 2026-09-14 10:57 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  34. 2026-09-13 22:19 UTCEG score recompute
  35. 2026-09-13 22:19 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  36. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  37. 2026-09-13 06:34 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  38. 2026-09-12 17:56 UTCEG score recompute
  39. 2026-09-12 17:56 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  40. 2026-09-12 05:17 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  41. 2026-09-11 16:38 UTCEG score recompute
  42. 2026-09-11 16:38 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  43. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  44. 2026-09-11 03:30 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  45. 2026-09-10 14:52 UTCEG score recompute
  46. 2026-09-10 14:52 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  47. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  48. 2026-09-09 08:51 UTCEG score recompute
  49. 2026-09-09 08:51 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  50. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  51. 2026-09-07 21:26 UTCEG score recompute
  52. 2026-09-07 21:26 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  53. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  54. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  55. 2026-09-06 08:13 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  56. 2026-09-05 19:33 UTCEG score recompute
  57. 2026-09-05 19:33 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  58. 2026-09-05 06:55 UTCEG score recompute
  59. 2026-09-05 06:55 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  60. 2026-09-04 12:55 UTCEG score recompute
  61. 2026-09-04 12:55 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  62. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  63. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  64. 2026-09-01 23:18 UTCEG score recompute
  65. 2026-09-01 23:18 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  66. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  67. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  68. 2026-08-31 01:38 UTCEG score recompute
  69. 2026-08-31 01:38 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  70. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  71. 2026-08-30 12:59 UTCEG score recompute
  72. 2026-08-30 12:59 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH
  73. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  74. 2026-08-30 00:20 UTCEG score recompute
  75. 2026-08-30 00:20 UTCGHSA enrichmentGHSA-6jqh-rgp9-536f · GitHub severity HIGH

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55732?
CVE-2026-55732 is a high-severity vulnerability; its CVE record was published on July 24, 2026. Out-of-bounds Read (CWE-125) in BACnet packet parsing (bacdtdatetimetotod) in Loytec LIP-ME201C, L-INX, L-GATE, L-ROC, L-IOB, L-DALI, L-VIS and L-PAD through 8.4.18 on LINX-A64 allows an unauthenticated remote attacker to crash linxa64.exe and ultimately reboot the device via a malformed BACnet…
When was the CVE record for CVE-2026-55732 published?
The CVE record for CVE-2026-55732 was published on July 24, 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 July 27, 2026; the record at its source may have been updated since.
Is CVE-2026-55732 actively exploited?
CVE-2026-55732 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55732?
CVE-2026-55732 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55732?
The CVE record's solution for CVE-2026-55732, written by its CNA Switzerland National Cyber Security Centre (NCSC), names the fix: "Upgrade to firmware version 8.4.20." The vendor advisories EchelonGraph has for CVE-2026-55732 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-55732?

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

Book a Demo →Browse All CVEs