BACNET STACK · CVE-2026-62975 · Package
NO FIX YET · SEE WHAT TO DO
BACnet Stack's RAMFS-backed file code, used in AtomicWriteFile record-access requests, can shrink a heap buffer and then copy using a stale length. An attacker can cause an out-of-bounds heap read, which can leak memory contents or crash the process.
first public Jul 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Only builds of BACnet Stack that use the RAMFS-backed FILE implementation and accept AtomicWriteFile record-access requests from clients are exposed. Systems that do not expose BACnet file services or do not use RAMFS can likely skip it, though the sources do not say which configurations are default.
Not affected if file-services-disabled, no-ramfs-file-backend
Who cares bacnet, c, embedded, iot
1.5.1.1.5.1 or 1.6.0, the patched versions named in the advisory.BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to version 1.5.1, the RAMFS-backed FILE implementation accepts AtomicWriteFile(record-access) requests that replace existing records with caller-controlled content. If a client replaces a record with shorter data, the backend can shrink the heap allocation and then continue processing with a trailing-copy length derived from the old layout. During that replace path, the RAMFS backend computes the trailing-copy length from the old file layout, then shrinks the heap allocation, and finally uses the stale length in memmove(). As a result, the source range of that memmove() can extend beyond the end of the reallocated heap buffer, producing a heap out-of-bounds read. This issue has been patched in versions 1.5.1 and 1.6.0.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.