CVE-2026-62972 · Package
NO FIX YET · SEE WHAT TO DO
BACnet Stack is a C library for building BACnet building-automation devices. A nested decode in its lighting command parser is given the wrong buffer size, so it reads past the end of the received packet, an out-of-bounds read.
first public Jul 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that build or run BACnet devices, gateways or tools on the BACnet Stack C library, especially embedded firmware that accepts BACnet lighting-control messages from the network. Systems that do not use this library or the lighting command service can skip it.
Not affected if lighting-service-unused, not-using-bacnet-stack
Who cares bacnet, building-automation, c, embedded
1.4.5, 1.5.1 and 1.6.0.lighting_command_decode in src/bacnet/lighting.c to confirm the vulnerable code is present.1.4.5, 1.5.1 or 1.6.0 depending on the release line in use.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, lighting_command_decode in src/bacnet/lighting.c decodes its first field with the bounded apdu_size - apdu_len, but every nested decode in the operation switch is called with the original full apdu_size while the read pointer has been advanced to &apdu[apdu_len]. The leaf decoders bound their reads against the size they are told, so they read up to apdu_len bytes past the end of the caller's buffer, resulting in an out-of-bounds read. 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:L/VI:N/VA:L/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.