cve.bz

CVE-2026-102537 bacnet-stack BACnet/SC node always accepts a self-signed hub cert, so an attacker can MITM it

7.7 high

High (7.7) in bacnet-stack bacnet-stack.

On this page
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.

Severity

CVSS 4.0

7.7 high
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-102537 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102537?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102537?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102537 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-102537

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-102537](https://cve.bz/cve/badge/CVE-2026-102537.svg)](https://cve.bz/cve/CVE-2026-102537)

HTML:

<a href="https://cve.bz/cve/CVE-2026-102537"><img src="https://cve.bz/cve/badge/CVE-2026-102537.svg" alt="CVE-2026-102537"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
bacnet-stack< 1.4.6
bacnet-stack>= 1.5.0, < 1.5.2
bacnet-stack>= 1.6.0, < 1.6.1

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON