CVSS 3.1
8.2 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:HCVE-2026-45265 Atomic-Read-File RecordCount Stack-Based Out-of-Bounds Write in bacnet-stack
High (8.2) in bacnet-stack bacnet-stack. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
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.
Severity
- EPSS
- 0.3% estimated probability of exploitation activity in the next 30 days; 18th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-121 Stack-based Buffer Overflow
- Published
- Modified
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-45265 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-45265?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-45265?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-45265 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-45265)
HTML:
<a href="https://cve.bz/cve/CVE-2026-45265"><img src="https://cve.bz/cve/badge/CVE-2026-45265.svg" alt="CVE-2026-45265"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| bacnet-stack | < 1.4.4 |
| bacnet-stack | < 1.5.1 |