CVE
BACnet Stack remote denial of service in ReadPropertyMultiple handler
Affects bacnet-stack when it processes a malformed ReadPropertyMultiple request that lacks the expected closing tags. Fixed in 1.4.5, 1.5.1, and 1.6.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Exploited
- No known exploitation
- Fix
- Fixed in 1.4.5, 1.5.1, 1.6.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.4.5, 1.5.1, 1.6.0.
- 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
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.29% · 21st percentile
- 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? →
- 25/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
Malformed ReadPropertyMultiple requests sent to the BACnet Stack library can cause its handler to enter an infinite loop, making the software stop responding. The attack can be carried out over the network without logging in.
Original description
BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.5, 1.5.1, and 1.6.0, a Denial of Service (DoS) vulnerability exists in the BACnet stack's ReadPropertyMultiple (RPM) handler. When processing a malformed RPM request packet that lacks the expected closing tags, the function handler_read_property_multiple enters an infinite loop. This issue has been patched in versions 1.4.5, 1.5.1, and 1.6.0.
Who should check
Teams running bacnet-stack before 1.4.5, 1.5.1 or 1.6.0 in building automation or industrial control systems
“A Denial of Service (DoS) vulnerability exists in the BACnet stack's ReadPropertyMultiple (RPM) handler.”
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
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.4.5, 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-52789 (BACnet Stack: Denial of Service (Infinite Loop) in handler_read_property_multiple via malformed RPM requests), 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-52789 (entry last updated 2026-11-13):
Affected:
- bacnet-stack bacnet-stack: fixed in 1.4.5; fixed in 1.5.1; fixed in 1.6.0
Fixed versions: 1.4.5, 1.5.1, 1.6.0.
Conditions (all must be true for the bug to be hit):
- A malformed ReadPropertyMultiple request packet that lacks the expected closing tags is processed by the stack (source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-4rf9-4vgq-5gcw)
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-52789 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-52789 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-4rf9-4vgq-5gcw
- https://github.com/bacnet-stack/bacnet-stack/pull/1374
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-52789
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-52789"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- bacnet-stack bacnet-stack
fixed in 1.4.5; fixed in 1.5.1; fixed in 1.6.0
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-52789
Is CVE-2026-52789 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 malformed ReadPropertyMultiple request packet that lacks the expected closing tags can make the BACnet server thread hang in an infinite loop. The thread then consumes 100% CPU, which is a denial of service.Source: github.com
Which versions are affected by CVE-2026-52789?
bacnet-stack: before 1.4.5; before 1.5.1; before 1.6.0.Source: cve.now feed data
Am I affected, and how do I check?
The affected product is bacnet-stack, and the fixed releases named in the facts are 1.4.5, 1.5.1, and 1.6.0. To check a installation, compare the bacnet-stack version in use against those fixed releases.Source: github.com
How do I fix CVE-2026-52789?
Move to a fixed release: 1.4.5, 1.5.1, or 1.6.0, matching your release line.Source: github.com