Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify BACnet/IP-exposed Loytec LINX-A64 device
-
DeliverySend malformed TimeSynchronization APDU with invalid month value
-
ExploitTrigger OOB read in bacdt_datetime_to_tod
-
ExecutionCrash linx_a64.exe process
-
ImpactDevice reboots causing building automation DoS
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network-level reachability to a Loytec LINX-A64 device running firmware 8.4.18 or earlier over BACnet/IP (typically UDP port 47808). No authentication is required (CVSS PR:N). The BACnet TimeSynchronization service must be reachable from the attacker's network - a service that is standard-on for these building controllers. What limits real-world exploitation: BACnet devices are architecturally intended for isolated OT/BAS network segments, and most properly secured deployments do not expose UDP 47808 to untrusted or internet-facing networks; correct network segmentation eliminates the attack vector entirely. The vulnerability is availability-only - no code execution, privilege escalation, or data exfiltration capability is established by available data. |
| Impact | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H) is well-calibrated for this vulnerability: network-accessible, no authentication, no complexity threshold, but impact strictly limited to availability with zero confidentiality or integrity consequence. EPSS at 0.32% (25th percentile) and SSVC exploitation status 'none' together indicate no observed or imminent exploitation at time of analysis. The SSVC 'automatable: yes' designation is the most operationally significant signal - a single malformed UDP packet to port 47808 is sufficient to crash any reachable device, and mass scanning is trivially scriptable. In OT/BAS contexts, even a brief availability loss in a mid-sized facility in mielec could cause HVAC outages, lighting failures, or access control disruptions with real physical consequences, making deployment context the primary risk multiplier. The input tags 'Buffer Overflow' and 'Information Disclosure' are inaccurate for this vulnerability, which is a read-triggered crash with no confirmed write primitive and no confidentiality impact per CVSS VC:N - this overstates the technical capability of the flaw. Real-world exploitability is strongly gated by whether BACnet/IP is reachable from untrusted networks; properly segmented OT environments face negligible exposure. |
| Exploit ScenarioDerived | An attacker with network access to BACnet/IP (UDP port 47808) on an unpatched Loytec LINX-A64 device crafts a BACnet APDU with the TimeSynchronization service code and sets the month field to an invalid value such as 0x00 or 0xFF. Upon receipt, |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 16, 2026
Remote denial-of-service in Loytec LINX-A64-based building automation controllers through firmware 8.4.18 allows an unauthenticated network attacker to crash the linx_a64.exe process and reboot the device by sending a single malformed BACnet TimeSynchronization or UTC-TimeSynchronization packet carrying an invalid month value. The root cause is an out-of-bounds read (CWE-125) in bacdt_datetime_to_tod during datetime parsing, with no authentication barrier and no user interaction required. No public exploit or active exploitation has been identified at time of analysis, but the SSVC automatable classification means mass scanning and crashing of exposed BACnet devices is trivially scriptable.
RemediationAI
Upgrade all affected Loytec LINX-A64-based devices to firmware above version 8.4.18 per the Loytec vendor advisory at https://www.loytec.com/support/product-security/advisories/8532-dibt-cve-20260608-0001-bacnet-crash-due-to-invalid-timesync-message-high. Note that the specific patched firmware version number is not independently confirmed in available data beyond the advisory title's implication that versions above 8.4.18 address the issue - verify the exact target version with Loytec support before deploying. As an immediate compensating control, isolate affected devices on dedicated OT/BAS network segments and block BACnet/IP traffic (UDP port 47808) from all untrusted networks at the perimeter firewall or industrial DMZ. Additionally, restrict TimeSynchronization message sources using BACnet BBMD and firewall ACLs to only trusted NTP masters or BACnet time servers within the controlled segment - this eliminates the attack vector without disrupting legitimate time synchronization. Note that overly broad firewall rules may also block legitimate BACnet services from integration platforms; audit BACnet traffic flows before applying port-level blocking.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 8 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
BACnet (ASHRAE/ANSI 135) is the dominant building automation and control network protocol used in HVAC, lighting, access control, and related OT systems. The vulnerable function bacdt_datetime_to_tod performs datetime-to-time-of-day conversion within the BACnet stack embedded in Loytec's LINX-A64 firmware. When a TimeSynchronization or UTC-TimeSynchronization service request arrives with a month value outside the valid range (1-12), the function reads past the intended buffer boundary (CWE-125) without adequate input validation, causing an exception that terminates the linx_a64.exe process and triggers a device reboot. The affected CPE strings span the entire LINX-A64 product family: cpe:2.3:a:loytec:lip-me20xc, cpe:2.3:a:loytec:l-inx, cpe:2.3:a:loytec:l-gate, cpe:2.3:a:loytec:l-roc, cpe:2.3:a:loytec:l-iob, cpe:2.3:a:loytec:l-dali, cpe:2.3:a:loytec:l-vis, and cpe:2.3:a:loytec:l-pad, all through version 8.4.18.
Know when Lip Me20Xc gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Single malformed BACnet packet over network, no authentication; impact limited entirely to availability (crash/reboot) with no confidentiality or integrity effect.
Primary rating from Vendor (NCSC.ch).
CVSS VectorVendor: NCSC.ch
DescriptionCVE.org
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.
Executive ViewAI
Loytec LINX-A64 building automation controllers (firmware 8.4.18 and earlier) are vulnerable to remote denial-of-service attacks that crash critical systems-HVAC, lighting, and access control-affecting facility operations across potentially thousands of deployed installations with no authentication required. A single malformed network packet from an unauthenticated attacker can trigger device reboot, creating operational risk to climate control and physical security infrastructure. No vendor patch is currently available, necessitating immediate network-level mitigation.
No vendor-released patch identified at time of analysis. Implement network segmentation restricting BACnet protocol (UDP 47808) access to trusted facility management networks only; deploy firewall ACLs and rate limiting on BACnet endpoints; establish continuous monitoring of controller logs for anomalous reboots and unexpected device state changes; subscribe to Loytec security advisories for patch notifications.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
More in Lip Me20Xc
View allLocal privilege escalation in Loytec building-automation controllers (L-INX, L-GATE, L-ROC, L-IOB, L-DALI, L-VIS, L-PAD
Stored XSS in the OPC XML-DA server statistics endpoint of multiple Loytec building automation devices allows an unauthe
We are tasked with producing a comprehensive analysis of CVE-2026-12504 in JSON format. We have description, CVSS 4.0 ve
A local privilege escalation flaw in the ltsudo binary on Loytec LIP-ME201C and related L-Series building automation con
Persistent denial of service in Loytec LIP-ME201C and related building automation controllers through version 8.4.16 all
Privilege escalation in Loytec ltsudo utility on LIP-ME201C, L-INX, L-GATE, L-ROC, L-IOB, L-DALI, L-VIS, and L-PAD throu
EUVD-2026-48597
GHSA-6jqh-rgp9-536f
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB