CVE-2026-41475 | bacnet-stack BACnet Stack up to 1.4.2 WritePropertyMultiple Service wpm_decode_object_property out-of-bounds (GHSA-cvv4-v3g6-4jmv / EUVD-2026-25621)

VDB-359562 · CVE-2026-41475 · GHSA-CVV4-V3G6-4JMV BACNET-STACK BACNET STACK UP TO 1.4.2 WRITEPROPERTYMULTIPLE SERVICE WPM_DECODE_OBJECT_PROPERTY OUT-OF-BOUNDS HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.1 $0-$5k 3.94+ Summaryinfo A vulnerability classified as problematic was found in bacnet-stack BACnet Stack up to 1.4.2. Impacted is the function wpm_decode_object_property of the component WritePropertyMultiple Service. The manipulation results in out-of-bounds. This vulnerability is reported as CVE-2026-41475. The attack can be launched remotely. No exploit exists. Upgrading the affected component is advised. Detailsinfo A vulnerability, which was classified as problematic, was found in bacnet-stack BACnet Stack up to 1.4.2. Affected is the function wpm_decode_object_property of the component WritePropertyMultiple Service. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on availability. CVE summarizes: BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to 1.4.3, an out-of-bounds read vulnerability in bacnet-stack's WritePropertyMultiple service decoder allows unauthenticated remote attackers to read past allocated buffer boundaries by sending a truncated WPM request. The vulnerability stems from wpm_decode_object_property() calling the deprecated decode_tag_number_and_value() function, which performs no bounds checking on the input buffer. 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. This vulnerability is fixed in 1.4.3. The advisory is available at github.com. This vulnerability is traded as CVE-2026-41475 since 04/20/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit. Upgrading to version 1.4.3 eliminates this vulnerability. The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-25621). Productinfo Vendor bacnet-stack Name BACnet Stack Version 1.4.0 1.4.1 1.4.2 CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 5.3 VulDB Meta Temp Score: 5.1 VulDB Base Score: 5.3 VulDB Temp Score: 5.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Out-of-bounds CWE: CWE-125 / CWE-119 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: BACnet Stack 1.4.3 Timelineinfo 04/20/2026 CVE reserved 04/24/2026 +4 days Advisory disclosed 04/24/2026 +0 days VulDB entry created 04/25/2026 +0 days VulDB entry last update Sourcesinfo Advisory: GHSA-cvv4-v3g6-4jmv Status: Confirmed CVE: CVE-2026-41475 (🔒) GCVE (CVE): GCVE-0-2026-41475 GCVE (VulDB): GCVE-100-359562 EUVD: 🔒 Entryinfo Created: 04/24/2026 23:07 Updated: 04/25/2026 00:53 Changes: 04/24/2026 23:07 (69), 04/25/2026 00:53 (1) Complete: 🔍 Cache ID: 99:D6A:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸