Is CVE-2026-45265 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-45265 being exploited in the wild.

How severe is CVE-2026-45265?

High severity, with a CVSS score of 8.2, published 12 November 2026.

Is there a fix for CVE-2026-45265?

Yes: fixed in 1.4.4, 1.5.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-45265 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-45265?

Check whether you run BACnet Stack at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-45265: bacnet-stack stack-based buffer overflow in Atomic-Read-File

CVE-2026-45265 · Severity: high · CVSS 8.2 · Published 2026-11-12

bacnet-stack is a protocol library used in embedded building automation systems to handle network communications. A malicious network request can cause the server to write beyond stack memory boundaries, potentially crashing the system or allowing remote code execution. The vulnerability is triggered when processing specially crafted file read requests from the network.

Technologies: BACnet Stack. Vendors: BACnet Stack.

Quick answers

Is CVE-2026-45265 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-45265 being exploited in the wild.
How severe is CVE-2026-45265?: High severity, with a CVSS score of 8.2, published 12 November 2026.
Which products and versions are affected?: BACnet Stack <1.4.4, <1.5.1.
Is there a fix for CVE-2026-45265?: Yes: fixed in 1.4.4, 1.5.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-45265 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-45265?: Check whether you run BACnet Stack at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 1.4.4, 1.5.1

Technical details

A stack-based out-of-bounds write occurs in the handler_atomic_read_file function when processing Atomic-Read-File requests in record access mode. An attacker can send a crafted request with an excessively large RecordCount value that exceeds the bounds of a stack-allocated BACNET_ATOMIC_READ_FILE_DATA structure containing only one fileData element; when the loop attempts to write to fileData[1], memmove() writes beyond the allocated buffer. The vulnerability requires network access to the BACnet server and affects versions prior to 1.4.4 and 1.5.1.

Affected products

bacnet-stack bacnet-stack <1.4.4, <1.5.1

Timeline

2026-11-12: disclosed
2026-05-08: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.