Quick answers
- Is CVE-2026-46676 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46676 being exploited in the wild.
- How severe is CVE-2026-46676?
- Medium severity, with a CVSS score of 5.3, published 12 November 2026.
- Which products and versions are affected?
- BACnet Stack 1.4.0 to 1.4.3, 1.5.0.
- Is there a fix for CVE-2026-46676?
- 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-46676 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-46676?
- 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
An uninitialized value use vulnerability exists in the AtomicReadFile record-access ACK encoder where stack-allocated BACNET_ATOMIC_READ_FILE_DATA objects are encoded without guaranteeing full initialization of BACNET_OCTET_STRING metadata. An unauthenticated remote attacker can send a crafted AtomicReadFile request that triggers a successful record-access path, causing the encoder to consume uninitialized length values that corrupt both the encoded OCTET STRING length semantics and payload copy boundary in network responses. On systems with partially initialized record buffers, this becomes a conditional information disclosure primitive. Patches are available in versions 1.4.4 and 1.5.1.
Affected products
- BACnet Stack BACnet Stack 1.4.0 to 1.4.3, 1.5.0
Timeline
- 2026-11-12: disclosed
- 2026-05-13: patched