CVE-2026-52788 · Package
NO FIX YET · SEE WHAT TO DO
BACnet Stack's URL parser for BACnet/SC Address Resolution messages writes past a fixed-size array when it reads space-separated WebSocket URIs. An attacker who can send such a message to a device can corrupt memory, which may allow code execution.
first public Jul 5, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Applications and embedded devices built on the BACnet Stack C library that use the BACnet/SC datalink with WebSocket address resolution. Systems that do not compile in BACnet/SC, or that run only BACnet/IP or MS/TP, are likely not exposed. The sources do not say whether the flaw is reachable without authentication.
Not affected if bacnet-ip-or-mstp-only, no-bacnet-sc
Who cares bacnet, building-automation, c, embedded
unknown if the sources do not say how to read it.bsc_node_parse_urls in src/bacnet/datalink/bsc/bsc-node.c of your copy of the library.1.4.5, 1.5.1 or 1.6.0 (the patched release in each series).BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.5, 1.5.1, and 1.6.0, the bsc_node_parse_urls() function in src/bacnet/datalink/bsc/bsc-node.c contains three distinct bugs when parsing space-separated WebSocket URIs from a BACnet/SC Address Resolution ACK message. Two bugs cause out-of-bounds writes past the utf8_urls[10][129] array in the static BSC_ADDRESS_RESOLUTION structure. This issue has been patched in versions 1.4.5, 1.5.1, and 1.6.0.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.