CVE
BACnet Stack: Stack buffer overflow in Loop internal ReadProperty path via Life_Safety_Zone.accepted-modes on the default BACnet/IP server
Affects bacnet-stack up to and including 1.6.0-rc1 when the default demo server creates loop-1 and life-safety-zone-1. Fixed in 1.4.4, 1.5.1, and 1.6.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.4.4, 1.5.1, 1.6.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.4.4, 1.5.1, 1.6.0.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
BACnet Stack, a C library for embedded systems, has a flaw in its default BACnet/IP server that lets a remote attacker crash it over the network without logging in. The attacker does this by sending a valid Confirmed WriteProperty request that points loop-1's controlled-variable-reference at life-safety-zone-1's accepted-modes, which triggers a stack buffer overflow.
Read the original 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, the current master demo server can be crashed remotely over BACnet/IP by sending a valid Confirmed WriteProperty request that updates loop-1's controlled-variable-reference to point to life-safety-zone-1 / accepted-modes. This issue has been patched in versions 1.4.4, 1.5.1, and 1.6.0.
Who should check
Teams running the bacnet-stack demo server or any bacnet-stack build with loop and life-safety-zone objects exposed over BACnet/IP.
Read the source excerpt
“The current master demo server can be crashed remotely over BACnet/IP”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.4.4, 1.5.1, 1.6.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-47711 (BACnet Stack: Stack buffer overflow in Loop internal ReadProperty path via Life_Safety_Zone.accepted-modes on the default BACnet/IP server), 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-47711 (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):
- The demo server (apps/server) creates loop-1 and life-safety-zone-1 by default. (source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-vrpm-9gm2-x552)
- Affected versions up to and including 1.6.0-rc1. (source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-vrpm-9gm2-x552)
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-47711 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-47711 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-vrpm-9gm2-x552
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-47711
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-47711"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- bacnet-stack bacnet-stack
fixed in 1.4.4; fixed in 1.5.1; fixed in 1.6.0
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-47711
Is CVE-2026-47711 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: cve.now feed data
What does this mean?
A remote BACnet/IP client can crash the demo server process through a stack buffer overflow, which corrupts memory.Source: github.com
Which versions are affected by CVE-2026-47711?
bacnet-stack: before 1.4.4; before 1.5.1; before 1.6.0.Source: cve.now feed data
Am I affected, and how do I check?
Versions up to and including 1.6.0-rc1 are affected. The demo server (apps/server) creates loop-1 and life-safety-zone-1 by default, so check the bacnet-stack version in use and whether those objects exist in the server configuration.Source: github.com
How do I fix CVE-2026-47711?
Upgrade to a fixed release: 1.4.4 for the 1.4 line, 1.5.1 for the 1.5 line, or 1.6.0 or later for the 1.6 line.Source: github.com