CVE-2026-47711
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
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.
Published Updated Sources: NVD, bacnet-stack (CNA), GitHub, SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Reported
not confirmed by CISA
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
8.6
high
Remediation
The vendor's own words where we have them.
Upgrade Bacnet-stack to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| Bacnet-Stack | bacnet-stack | < 1.4.4 | Vulnerable |
| Bacnet-Stack | bacnet-stack | < 1.5.1 | Vulnerable |
| Bacnet-Stack | bacnet-stack | < 1.6.0 | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
High
Confidentiality
Low
Integrity
Low
Scope
Unchanged
Attack Complexity
Low
Attack Vector
Network
Privileges Req
None
User Interaction
None
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 8.6 | CVSS 3.1 | high | 3.9 | 4.7 | GitHub (CNA), bacnet-stack (CNA) |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
What this weakness leads to
MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.
CWE-131 · Incorrect Calculation of Buffer Size
- DoS: Crash, Exit, or Restart
- Execute Unauthorized Code or Commands
- Read Memory
- Modify Memory
Mitigation: When allocating a buffer for the purpose of transforming, converting, or encoding an input, allocate enough memory to handle the largest possible encoding. For example, in a routine that converts & characters to & for HTML entity encoding, the output buffer needs to be at least 5 times as large as the input buffer.
CWE-805 · Buffer Access with Incorrect Length Value
- Read Memory
- Modify Memory
- Execute Unauthorized Code or Commands
- DoS: Crash, Exit, or Restart
Mitigation: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
Weakness & attack patterns
- CWE-121Stack-based Buffer Overflow
- CWE-131
- CWE-787Out-of-bounds Write
- CWE-805
Inferred from the weakness class — not observed against this CVE.
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
PoC repos
2
1 of the 2 sampled are weaponized
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Search application, proxy, and WAF logs for requests touching /IP.
- Prioritize edge telemetry for network-reachable Bacnet-stack.
- Monitor for scanner or exploit-pattern traffic after 2 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 8.6 (AV:N)
Nov 12, 2026 · NVD
Initial · CVE published
Nov 12, 2026 · NVD
CVE published by NIST.
Nov 12, 2026 · SOCRadar CTI
References
1 on the record
- github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-vrpm-9gm2-x552
Exploit, Third Party Advisory, NIST, Mitre
Elsewhere on this site
- Bacnet-Stackevery CVE for this vendor
- bacnet-stackevery page on this product
- Memory Corruptionsame class
- CWE-121other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-47711 is BACnet Stack: Stack buffer overflow in Loop internal ReadProperty path via Life_Safety_Zone.accepted-modes on the default BACnet/IP server, a high vulnerability affecting Bacnet-stack from Bacnet-stack. The current evidence does not list it in CISA KEV, and the exploit status is: Exploitation is reported, but no independent confirmation is available in the sources we have. Public exploit evidence is: 2 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8.6 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.