Skip to main content

Loytec LINX CVE-2026-55732

| EUVDEUVD-2026-48597 HIGH
Out-of-bounds Read (CWE-125)
2026-07-24 NCSC.ch GHSA-6jqh-rgp9-536f
8.7
CVSS 4.0 · Vendor: NCSC.ch
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify BACnet/IP-exposed Loytec LINX-A64 device
  2. Delivery
    Send malformed TimeSynchronization APDU with invalid month value
  3. Exploit
    Trigger OOB read in bacdt_datetime_to_tod
  4. Execution
    Crash linx_a64.exe process
  5. Impact
    Device 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, bacdt_datetime_to_tod performs an out-of-bounds read, causing linx_a64.exe to crash and forcing the controller to reboot, temporarily disabling whatever HVAC, lighting, or access control functions it manages. No authentication is required and no public exploit code has been identified, but the attack is a single-packet operation easily scripted for automated scanning of BACnet-exposed infrastructure.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

L-IOB 0 ≤8.4.18
L-GATE 0 ≤8.4.18
LIP-ME20xC 0 ≤8.4.18
L-VIS 0 ≤8.4.18
L-PAD 0 ≤8.4.18
L-INX 0 ≤8.4.18
L-ROC 0 ≤8.4.18
L-DALI 0 ≤8.4.18

Affected Packages

euvd l_dali no fix
euvd l_gate no fix
euvd l_inx no fix
euvd l_iob no fix
euvd l_pad no fix
euvd l_roc no fix
euvd l_vis no fix
euvd lip_me20xc no fix

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

Vendor (NCSC.ch) PRIMARY 8.7 HIGH
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
vuln.today AI 7.5 HIGH

Single malformed BACnet packet over network, no authentication; impact limited entirely to availability (crash/reboot) with no confidentiality or integrity effect.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (NCSC.ch).

CVSS VectorVendor: NCSC.ch

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

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

Why It Matters

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.

Business Impact: High
Compensating Controls

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

EPSS Score
0.3%
Top 75% exploitable
Prevalence
Low
niche industrial building automation controllers, not general-purpose IT infrastructure
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy