CVE-2026-45265: Atomic-Read-File RecordCount Stack-Based Out-of-Bounds Write in bacnet-stack
CVE-2026-45265 · HIGH 8.2 Atomic-Read-File RecordCount Stack-Based Out-of-Bounds Write in bacnet-stack
Summary: Atomic-Read-File RecordCount Stack-Based Out-of-Bounds Write in bacnet-stack
EPSS: 0.3% probability of exploitation in the next 30 days (percentile 17.7).
BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.4 and 1.5.1, there is a stack-based out-of-bounds write / stack-buffer-overflow in bacnet-stack when the server processes a malicious Atomic-Read-File request in record access mode. The bug is triggered on the real server side. A crafted request can set an excessively large RecordCount, which is later used as the loop bound for writing record data into a stack-allocated BACNET_ATOMIC_READ_FILE_DATA data structure. However, the stack object only has space for one fileData element. When the loop reaches i = 1, the code computes &data->fileData[1], which is already out of bounds, and the resulting invalid pointer is passed down to memmove(), causing a stack-buffer-overflow. This issue has been patched in versions 1.4.4 and 1.5.1.
HIGH (CVSS 8.2) — vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
CVE-2026-45265 · HIGH 8.2 Atomic-Read-File RecordCount Stack-Based Out-of-Bounds Write in bacnet-stack