CVE-2026-41475 is an out-of-bounds read (CWE-125) in bacnet-stack, the open-source BACnet C library for embedded systems: before 1.4.3, a truncated WritePropertyMultiple request from an unauthenticated sender makes the decoder read 1 to 7 bytes past its buffer, crashing or leaking memory on embedded BACnet devices. NVD scores it 9.1. Fixed in 1.4.3 and 1.5.0.
Vulnerability summary
CVSS base score
9.1
Critical severity
EPSS score (FIRST)
0.5%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2026-41475 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| bacnet-stack (WritePropertyMultiple service decoder, wpm_decode_object_property) | cpe:2.3:a:bacnetstack:bacnet_stack:*:*:*:*:*:*:*:* | 1.4.0 to before 1.4.3 and 1.5.0 rc1 to rc3 (NVD); fixed in 1.4.3 and 1.5.0, released 2026-04-16 (GHSA-cvv4-v3g6-4jmv, bacnet-stack CHANGELOG) |
| Embedded BACnet controllers and gateways whose firmware is built on bacnet-stack | — | per vendor firmware; affected when the bundled bacnet-stack is older than 1.4.3 and the WritePropertyMultiple handler is enabled (GHSA-cvv4-v3g6-4jmv) |
What does this mean for affected devices?
CVE-2026-41475 is in the WritePropertyMultiple (WPM) decoder of bacnet-stack, which describes itself as a "BACnet open source protocol stack C library for embedded systems". NVD's description says wpm_decode_object_property() calls the deprecated decode_tag_number_and_value() function, "which performs no bounds checking on the input buffer", so "a crafted BACnet/IP packet with a truncated property payload causes the decoder to read 1-7 bytes past the end of the buffer, leading to crashes or information disclosure on embedded BACnet devices." NVD records CWE-125 and its own Primary CVSS v3.1 score of 9.1 (critical), vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H (NVD). GitHub, the CNA, scores it 8.7 in CVSS v4.0 with availability impact only.
How does the truncated request trigger the read?
By ending right after the first tag. The project's advisory GHSA-cvv4-v3g6-4jmv walks through the code in src/bacnet/wpm.c: after decoding the property identifier, the function calls decode_tag_number_and_value() again to look for the optional array index "without any check that the current position len is still within the buffer boundary". With a 2-byte input, the first tag consumes both bytes and the second call reads past the end. The advisory notes that the WritePropertyMultiple service handler is "enabled by default in the reference server", and WritePropertyMultiple needs no authentication on plain BACnet/IP. CISA's SSVC entry in the CVE record, dated 2026-04-27, lists exploitation as "poc" and the attack as automatable.
Which versions and devices are affected?
NVD's CPE configuration lists bacnet-stack 1.4.0 to before 1.4.3 and 1.5.0 rc1 to rc3. The GitHub advisory states that all versions using wpm_decode_object_property() with the deprecated decoder are affected, so older forks are worth checking too. The fix came from PR #1244, which replaced the deprecated decoders in many service decoders. The 1.4.3 CHANGELOG, dated 2026-04-16, lists it under Security as securing "WritePropertyMultiple service decoders"; 1.5.0 was released the same day with the same change.
No device vendor or CISA ICS advisory naming a product affected by this CVE was found (CISA's CSAF advisory set checked 2026-11-17). The device angle comes from how the library ships: it is compiled into controller and gateway firmware, so each product carries whatever version its maker forked. The project's SECURITY.md lists 1.4.x, 1.6.x, 1.7.x and 1.8.x as supported, and marks 1.5.x and 1.3.x and older as unsupported, so firmware built on those branches needs a move to a supported branch.
What should firmware teams and building owners do?
Find the bacnet-stack version in each product. Our BACnet protocol security guide lists this CVE among the stack's decoder bugs that ship inside controllers, and a firmware SBOM is how a maker answers which version each product line carries. The companion WriteProperty bug is CVE-2026-26264, fixed in the same releases; the older CVE-2019-12480 is a similar crash in 0.8.6. For the weakness class, see our memory corruption fix guide.
CVE-2026-41475 is not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.00482, the 42nd percentile, in the 2026-11-16 dataset (CISA KEV, FIRST EPSS).
To fix it, rebuild firmware on bacnet-stack 1.4.3 or later on the 1.4 branch, or the newest release of a supported branch; SECURITY.md lists further decoder fixes in later 1.4.x releases. Device owners should ask the maker for firmware with a patched stack and, until then, keep BACnet/IP (commonly UDP 47808) reachable only from the building management network.
Evidence
- Before 1.4.3, wpm_decode_object_property() calls deprecated decode_tag_number_and_value() with no bounds check; truncated WPM request reads 1-7 bytes past the buffer; crashes or information disclosure on embedded BACnet devices; NVD Primary CVSS v3.1 9.1; CWE-125; CPE 1.4.0 to before 1.4.3 and 1.5.0 rc1-rc3; GitHub CVSS v4.0 8.7; CISA SSVC 2026-04-27 exploitation poc, automatable yes. — NVD
- Second decode call has no check that len is within apdu_len; a 2-byte input triggers the over-read; WPM handler enabled by default in the reference server; all versions using the deprecated decoder in wpm_decode_object_property() affected; patched 1.4.3 and 1.5.0. — GHSA-cvv4-v3g6-4jmv
- 1.4.3 (2026-04-16) Security: secured WritePropertyMultiple service decoders by replacing deprecated decoders (#1244). — bacnet-stack CHANGELOG 1.4.3
- Supported branches 1.8.x, 1.7.x, 1.6.x, 1.4.x; 1.5.x and 1.3.x and older unsupported; CVE-2026-41475 patched in 1.5.0 and 1.4.3 via PR #1244. — bacnet-stack SECURITY.md
- Not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). — CISA KEV
- EPSS 0.00482 (42nd percentile), dataset 2026-11-16, read 2026-11-17. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Does CVE-2026-41475 need authentication?
No. A truncated WritePropertyMultiple request on plain BACnet/IP reaches the decoder without any login, and NVD's vector has no privileges and no user interaction (per NVD and GHSA-cvv4-v3g6-4jmv).
Which bacnet-stack version fixes CVE-2026-41475?
1.4.3 and 1.5.0, both released 2026-04-16. SECURITY.md marks 1.5.x unsupported, so 1.5 users should move to a supported branch (per the bacnet-stack CHANGELOG and SECURITY.md).
Which devices are affected by CVE-2026-41475?
Any controller or gateway whose firmware bundles bacnet-stack older than 1.4.3 with the WritePropertyMultiple handler enabled. No vendor advisory naming a product was found as of 2026-11-17, so ask each maker for the bundled version (per GHSA-cvv4-v3g6-4jmv).
Is CVE-2026-41475 in the CISA KEV catalog?
No, not as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.00482, the 42nd percentile, in the 2026-11-16 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?