Menu

Star on GitHub · 3.2k

CVE-2026-32666

7.5 · HIGH

WebCTRL systems that communicate over BACnet inherit the protocol's lack of network layer authentication.

Published Mar 21, 2026CWE-290EPSS 0.56%

Overview

CVE-2026-32666 is a high-severity vulnerability. It was published on March 21, 2026 and has a CVSS 3.1 base score of 7.5 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

WebCTRL systems that communicate over BACnet inherit the protocol's lack

of network layer authentication. WebCTRL does not implement additional

validation of BACnet traffic so an attacker with network access could

spoof BACnet packets directed at either the WebCTRL server or associated

AutomatedLogic controllers. Spoofed packets may be processed as

legitimate.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-32666?

CVE-2026-32666 is a high-severity vulnerability. It was published on March 21, 2026 and has a CVSS 3.1 base score of 7.5 (HIGH).

How severe is CVE-2026-32666?

This vulnerability has a CVSS 3.1 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2026-32666?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-32666?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-32666 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all