Read the docs

Stack-based out-of-bounds write in bacnet-stack Atomic-Read-File

Priority MEDIUM 41CWE-121Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · Low · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

bacnet-stack versions before 1.4.4 and before 1.5.1 are affected. A stack-based buffer overflow (CWE-121) occurs when the server processes an Atomic-Read-File request in record access mode, because an attacker-supplied RecordCount causes writes past a one-element stack structure. A remote, unauthenticated attacker can send a crafted request to corrupt the server's stack memory.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00259 17th percentileScored 2026-11-16
Fix Fixed bacnet-stack (bacnet-stack): 1.4.4, 1.5.1

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

VendorProductAffected versionsFixed inStatusSource
bacnet-stackbacnet-stackbefore 1.4.4; before 1.5.11.4.4, 1.5.1Patch availableCNA
  • bacnet-stack Vendorbacnet-stack Affected before 1.4.4; before 1.5.1 Fixed in 1.4.4, 1.5.1 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:bacnetstack:bacnet_stack:*:*:*:*:*:*:*:*——bacnet-stack
  • cpe:2.3:a:bacnetstack:bacnet_stack:*:*:*:*:*:*:*:* Versions — — ·bacnet-stack

Remediation

Update bacnet-stack to version 1.4.4 or 1.5.1, the fixed versions listed for this flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · CNA bacnet-stack (bacnet-stack) Fixed in 1.4.4, 1.5.1

Timeline

  1. 2026-11-12 Threatist record created from CVE-2026-45265
  2. 2026-11-13 CISA SSVC decision points changed

References

  • 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
See all 41 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences