Skip to main content
VulnerabilityPublished

CVE-2026-49990: bacnet-stack · Out-of-bounds Read

Affects bacnet-stackSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High : upgrade to 1.5.1 or 1.4.5 soon.

Data as of 13 Nov 2026, 16:05 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.18.6
Patch
Available – fixed in 1.5.1, 1.4.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 13 Nov 2026.

What to do

Upgrade bacnet-stack to 1.5.1 or 1.4.5.

Affected software

ProductAffectedFixed in
bacnet-stackbacnet-stackAffected
  • >=1.5.0 <1.5.1
Fixed in
  • 1.5.1
bacnet-stackbacnet-stackAffected
  • >=1.4.2 <1.4.5
Fixed in
  • 1.4.5

AI-suggested

Upgrade bacnet-stack to version 1.4.5 or later, or 1.5.1 or later, where this vulnerability has been patched. No other mitigations are specified or required once patched.

Description

CVE-2026-49990 is a high-severity vulnerability in the bacnet-stack open source BACnet protocol library for embedded systems. Versions 1.4.2 up to but not including 1.4.5, and 1.5.0 up to but not including 1.5.1, improperly validate a signed fileStartPosition parameter in AtomicReadFile and AtomicWriteFile stream-access requests. This leads to out-of-bounds reads and writes in RAM file backends, potentially causing process crashes, memory exposure, or heap corruption. The issue is fixed in versions 1.4.5 and 1.5.1.

References

Community reviews

Loading reviews…