Quick answers
- Is CVE-2026-47259 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47259 being exploited in the wild.
- How severe is CVE-2026-47259?
- High severity, with a CVSS score of 8.2, 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-47259?
- 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-47259 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-47259?
- 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-based out-of-bounds write occurs in Notification_Class_Remove_List_Element() when decoding a RemoveListElement request targeting the Notification-Class.recipient-list. The vulnerable function allocates a fixed-size stack buffer (NC_MAX_RECIPIENTS = 10 entries) but lacks bounds checking before decoding attacker-controlled BACnetDestination elements into this buffer via bacnet_destination_decode(). When a request contains more than 10 valid elements, the 11th element is written one past the buffer boundary. This is a network-accessible remote crash vulnerability affecting BACnet protocol implementations in embedded systems.
Affected products
- BACnet Stack BACnet Stack prior to 1.4.4, 1.5.1, and 1.6.0
Timeline
- 2026-11-12: disclosed
- 2026-05-18: patched