Unbounded buffer growth in BACnet Stack BACnet/SC hub
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-400.
Summary
BACnet Stack before 1.4.6, from 1.5.0 before 1.5.2, and from 1.6.0 before 1.6.1 is affected. The BACnet/SC hub's Linux WebSocket server keeps growing its fragment buffer for fragmented messages with no upper bound, which is uncontrolled resource consumption (CWE-400). A remote unauthenticated peer that sends binary continuation fragments without a final frame can exhaust the host's memory or get the process killed by the out-of-memory killer.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
Description from the CNA
BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.6, 1.5.2, and 1.6.1, the BACnet/SC hub's Linux WebSocket server reassembles fragmented WebSocket messages into a per-connection fragment_buffer. It grows that buffer with realloc() on every non-final frame, with no upper bound. A peer that streams binary continuation fragments and never sets FIN keeps the hub reallocating until the box runs out of memory or the process is OOM-killed. The buffer starts at the maximum legal BVLC-SC NPDU size, but nothing after that ties its growth back to that limit. This issue has been patched in versions 1.4.6, 1.5.2, 1.6.1, and 1.7.0.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| bacnet-stack | bacnet-stack | before 1.4.6; 1.5.0 to before 1.5.2; 1.6.0 to before 1.6.1 | 1.4.6, 1.5.2, 1.6.1 | Patch available | CNA |
- bacnet-stack Vendorbacnet-stack Affected before 1.4.6; 1.5.0 to before 1.5.2; 1.6.0 to before 1.6.1 Fixed in 1.4.6, 1.5.2, 1.6.1 Patch available CNA
CPE names Threatist (inferred) · 1
Inferred from how NVD named this product before; not given by a source.
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:bacnetstack:bacnet_stack:*:*:*:*:*:*:*:* | — | — | bacnet-stack |
- cpe:2.3:a:bacnetstack:bacnet_stack:*:*:*:*:*:*:*:* Versions — — ·bacnet-stack
Remediation
Upgrade bacnet-stack to version 1.4.6, 1.5.2, 1.6.1, or 1.7.0, which contain the patch.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
- Fix · CNA bacnet-stack (bacnet-stack) Fixed in 1.4.6, 1.5.2, 1.6.1
Timeline
- 2026-11-13 Threatist record created from CVE-2026-100403
References
More bacnet-stack vulnerabilities
- TI-2026-91748 Unbounded resize in BACnet Stack Structured View allows denial of service CVSS 4.0HIGH 8.7
- TI-2026-30089 BACnet Stack: Out-of-Bounds Read in ReadPropertyMultiple Property Decoder via Deprecated Tag Parser CVSS 4.0HIGH 8.7
- TI-2026-30088 BACnet Stack: Off-by-One Out-of-Bounds Read in ReadPropertyMultiple Object ID Decoder CVSS 4.0HIGH 8.7
- TI-2026-30063 BACnet Stack: Out-of-Bounds Read in WritePropertyMultiple Decoder via Deprecated Tag Parser CVSS 4.0HIGH 8.7
- TI-2026-91002 Stack-buffer-overflow in BACnet Stack Loop object description handling CVSS 3.1HIGH 8.2
- TI-2026-91000 Stack-based buffer overflow in BACnet Stack Notification Class CVSS 3.1HIGH 8.2
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences