CVE-2026-45265: bacnet-stack · Stack-based Buffer Overflow
Affects bacnet-stackSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 1.5.1 or 1.4.4 soon.
Data as of 12 Nov 2026, 20:47 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 8.2 |
|---|
- Patch
- Available – fixed in 1.5.1, 1.4.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade bacnet-stack to 1.5.1 or 1.4.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| bacnet-stackbacnet-stack | Affected
| Fixed in
|
| bacnet-stackbacnet-stack | Affected
| Fixed in
|
AI-suggested
Upgrade bacnet-stack to version 1.4.4 or 1.5.1 or later, where this vulnerability has been fixed. No other mitigation is required as the issue is resolved in these official releases.
Description
A stack-based buffer overflow vulnerability exists in bacnet-stack prior to versions 1.4.4 and 1.5.1. The flaw occurs when the server processes a malicious Atomic-Read-File request with an excessively large RecordCount, causing out-of-bounds writes on the stack. This can lead to a stack-buffer-overflow due to improper bounds checking on a stack-allocated data structure. The issue has been fixed in versions 1.4.4 and 1.5.1.