---
id: "CVE-2026-82414"
page: "https://infrastack.ai/live/CVE-2026-82414"
kind: "vulnerability"
aliases: ["CVE-2026-82414"]
title: "BACnet Stack: long MS/TP frame overflows buffer, risking memory corruption"
severity: "high"
cvss: 8.8
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["bacnet-stack", "building-automation", "c", "embedded", "package"]
not_affected_if: ["bacnet-ip-only", "versions-outside-range"]
published_at: "2026-11-13T19:19:36+00:00"
first_seen_at: "2026-11-13T19:52:10+00:00"
updated_at: "2026-11-13T19:54:04+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-82414", "first_seen_at": "2026-11-13T19:52:10+00:00"}]
exploit_sources: []
---

# BACnet Stack: long MS/TP frame overflows buffer, risking memory corruption

Link for people: https://infrastack.ai/live/CVE-2026-82414 (this .md is for agents)

BACnet Stack is a C library for building BACnet building-automation devices. A long valid COBS-encoded MS/TP frame can be decoded past the end of its fixed input buffer, corrupting memory on the device.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the bacnet-stack version in the project, for example `git describe --tags` or the version in your build files, and compare against the fixed versions below.
- Look for the MS/TP receive path (COBS decoding) in your build of the library.

## Fix

- `1.4.6` for the 1.4.x line
- `1.5.1` for the 1.5.x line
- `1.6.1` for the 1.6.x line
- `1.7.0` includes the patch

## Timeline

- 2026-11-13T19:52:10+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-82414

## Documents

- [advisory] Vendor advisory: github.com https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-8456-m9x4-j6mc

## From the sources

BACnet Stack is a BACnet open source protocol stack C library for embedded systems. From versions 1.4.0 to before 1.4.6, 1.5.0 to before 1.5.1, and 1.6.0 to before 1.6.1, the BACnet MS/TP receive path decodes COBS frames into an output pointer inside the same fixed input buffer, but passes the full input-buffer size as the decode capacity. A long valid COBS payload can therefore write past the end of the actual remaining buffer. This issue has been patched in versions 1.4.6, 1.5.1, 1.6.1, and 1.7.0.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_