CVE-2026-62976

published 13 Nov 2026 · updated 16 Nov 2026

BACnet Stack: Consecutive AtomicWriteFile(record-access) appends can trigger a heap out-of-bounds read in the RAMFS file backend

8.7HighCVSS 8.7EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
bacnet-stack<1.5.1

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-62976 severity on Zeptric[![CVE-2026-62976](https://zeptric.io/badge/cve/CVE-2026-62976.svg)](https://zeptric.io/cve/CVE-2026-62976)