Quick answers
- Is CVE-2026-47711 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47711 being exploited in the wild.
- How severe is CVE-2026-47711?
- High severity, with a CVSS score of 8.6, published 12 November 2026.
- Which products and versions are affected?
- BACnet Stack prior to 1.4.4, 1.5.1, and 1.6.0.
- Is there a fix for CVE-2026-47711?
- Yes: fixed in 1.4.4, 1.5.1, 1.6.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47711 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-47711?
- Check whether you run BACnet Stack at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.4.4, 1.5.1, 1.6.0
Technical details
A stack buffer overflow exists in the Life_Safety_Zone property reading code path within the Loop object's timer callback. When a remote client sends a WriteProperty request to set loop-1's controlled-variable-reference to point to life-safety-zone-1's accepted-modes property, the subsequent timer tick calls Loop_Read_Variable_Reference_Update() which allocates a fixed 32-byte buffer, but Life_Safety_Zone_Read_Property() writes an unbounded number of enumerated values without length checking, overflowing the stack. The vulnerability is network-reachable on the default BACnet/IP demo server without requiring authentication.
Affected products
- BACnet Stack BACnet Stack prior to 1.4.4, 1.5.1, and 1.6.0
Timeline
- 2026-07-05: disclosed
- 2026-11-12: advisory