BACnet Stack RAMFS append causes heap out-of-bounds read in record counting
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-125 and the CVSS impact.
Summary
BACnet Stack, a BACnet protocol stack C library for embedded systems, is affected before version 1.5.1. In the RAMFS-backed FILE object implementation, appended records are stored as NUL-terminated strings, but record counting walks the buffer as if an extra empty terminating record existed. Two consecutive AtomicWriteFile(record-access) append requests can make record_count() call bacnet_strnlen() on a pointer one byte past the end of the heap allocation, causing a heap out-of-bounds read (CWE-125). The CVSS 4.0 base score is 8.7 (HIGH), with network attack vector and no privileges or user interaction required.
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 version 1.5.1, the RAMFS-backed FILE object implementation stores appended records as NUL-terminated strings, but its record-counting logic later walks the buffer as if an additional terminating empty record were present. As a result, two consecutive AtomicWriteFile(record-access) append requests can cause record_count() to call bacnet_strnlen() on a pointer that is already one byte past the end of the heap allocation. This issue has been patched in versions 1.5.1 and 1.6.0.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| bacnet-stack | bacnet-stack | before 1.5.1 | 1.5.1 | Patch available | CNA |
- bacnet-stack Vendorbacnet-stack Affected before 1.5.1 Fixed in 1.5.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.5.1 or 1.6.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.5.1
Timeline
- 2026-11-13 Threatist record created from CVE-2026-62976
- 2026-11-16 CISA SSVC decision points changed
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