cve.bz

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

8.2 highEPSS 0.3%

High (8.2) in bacnet-stack bacnet-stack. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 17th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-121 Stack-based Buffer Overflow
CWE-787 Out-of-bounds Write
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-47710 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-47710?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-47710?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-47710 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-47710

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-47710](https://cve.bz/cve/badge/CVE-2026-47710.svg)](https://cve.bz/cve/CVE-2026-47710)

HTML:

<a href="https://cve.bz/cve/CVE-2026-47710"><img src="https://cve.bz/cve/badge/CVE-2026-47710.svg" alt="CVE-2026-47710"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
bacnet-stack< 1.4.4
bacnet-stack< 1.5.1
bacnet-stack< 1.6.0

References

Check your stackJSON