Read the docs

BACnet/SC node in bacnet-stack accepts self-signed hub certificates

Priority LOW 35CWE-295Published · Updated

Key facts

Attack vector
Adjacent network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
Spoofing
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-295.

Summary

bacnet-stack versions before 1.4.6, from 1.5.0 before 1.5.2, and from 1.6.0 before 1.6.1 are affected. The Linux BACnet/SC connection code always allows self-signed certificates, so a node accepts a self-signed hub certificate even when it does not chain to the loaded CA (CWE-295). An attacker on the adjacent network can present a rogue hub, receive the node's VMAC and UUID, and read all later BACnet traffic.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.6, 1.5.2, and 1.6.1, bws_cli_connect() in ports/linux/websocket-cli.c loads the trusted CA cert into the libwebsockets context, then always sets LCCSCF_ALLOW_SELFSIGNED in the connection flags. So lws accepts any self-signed hub certificate, whether or not it chains to the loaded CA. A BACnet/SC node finishes the TLS handshake to a rogue hub that presents a self-signed cert. It then hands the attacker its identity (VMAC, UUID) and all later BACnet traffic. This issue has been patched in versions 1.4.6, 1.5.2, 1.6.1, and 1.7.0.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00201 10th percentileScored 2026-11-16
Fix Fixed bacnet-stack (bacnet-stack): 1.4.6, 1.5.2, 1.6.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
bacnet-stackbacnet-stackbefore 1.4.6; 1.5.0 to before 1.5.2; 1.6.0 to before 1.6.11.4.6, 1.5.2, 1.6.1Patch availableCNA
  • bacnet-stack Vendorbacnet-stack Affected before 1.4.6; 1.5.0 to before 1.5.2; 1.6.0 to before 1.6.1 Fixed in 1.4.6, 1.5.2, 1.6.1 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:bacnetstack:bacnet_stack:*:*:*:*:*:*:*:*——bacnet-stack
  • cpe:2.3:a:bacnetstack:bacnet_stack:*:*:*:*:*:*:*:* Versions — — ·bacnet-stack

Remediation

Upgrade bacnet-stack to version 1.4.6, 1.5.2, 1.6.1, or 1.7.0. The sources list no vendor advisory identifier for this fix.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA bacnet-stack (bacnet-stack) Fixed in 1.4.6, 1.5.2, 1.6.1

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-102537
  2. 2026-11-16 CISA SSVC decision points changed

References

  • TI-2026-91748 Unbounded resize in BACnet Stack Structured View allows denial of service CVSS 4.0HIGH 8.7
  • TI-2026-30089 BACnet Stack: Out-of-Bounds Read in ReadPropertyMultiple Property Decoder via Deprecated Tag Parser CVSS 4.0HIGH 8.7
  • TI-2026-30088 BACnet Stack: Off-by-One Out-of-Bounds Read in ReadPropertyMultiple Object ID Decoder CVSS 4.0HIGH 8.7
  • TI-2026-30063 BACnet Stack: Out-of-Bounds Read in WritePropertyMultiple Decoder via Deprecated Tag Parser CVSS 4.0HIGH 8.7
  • TI-2026-91002 Stack-buffer-overflow in BACnet Stack Loop object description handling CVSS 3.1HIGH 8.2
  • TI-2026-91000 Stack-based buffer overflow in BACnet Stack Notification Class CVSS 3.1HIGH 8.2
See all 41 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences