BACnet Stack: Out-of-bounds memory access (CVE-2026-49990)
BACnet Stack versions 1.4.2 to 1.4.4 and 1.5.0 are vulnerable to out-of-bounds memory access via unvalidated AtomicReadFile and AtomicWriteFile requests, potentially leading to denial of service or heap memory corruption.
CVE search metadata
CVE search record: CVE-2026-49990. Severity: high. CVSS: 8.6. EPSS: 0.33%. KEV: no. Product: BACnet Stack. Brief: BACnet Stack: Out-of-bounds memory access (CVE-2026-49990). Brief link: https://feed.craftedsignal.io/briefs/2026-11-cve-2026-49990/
Triage facts
Revision 1- Applicability
- BACnet Stack
- Evidence
- Unknown
- Severity
- High
- Action
- Elevated
- Sources
- 1 public source
- Freshness
- Revision 1Nov 14, 16:41 UTC
- Vulnerabilities
- 1 CVE
- Source quality
- A1Roughly even chance
Overview
BACnet Stack versions 1.4.2 to 1.4.4 and 1.5.0 contain a vulnerability where the fileStartPosition parameter in AtomicReadFile and AtomicWriteFile stream-access requests is not properly validated before reaching RAM file backends. Exploitation allows an attacker to trigger out-of-bounds memory read or write operations.
Impact
Successful exploitation can result in a denial of service through a process crash. Furthermore, the vulnerability enables out-of-bounds reads which may expose adjacent memory contents, and out-of-bounds writes which may corrupt heap memory, leading to process destabilization.
Recommendation
Inventory systems running BACnet Stack library components to identify those within the affected version ranges. Upgrade to BACnet Stack version 1.4.5 or 1.5.1 immediately to remediate this vulnerability.
Threat Hunt
Identify abnormal process terminations or frequent restarts in BACnet stack services following AtomicReadFile or AtomicWriteFile requests that contain anomalous fileStartPosition values.
Data: Process exit logs, Application service logs, Network packet capture containing BACnet stream-access requests
Mitigations
Upgrade BACnet Stack to version 1.4.5 or 1.5.1
CVE-2026-49990
Gaps
- Telemetry visibility into protocol-specific memory access violations is limited in standard embedded environments.