---
id: "CVE-2026-102612"
page: "https://infrastack.ai/live/CVE-2026-102612"
kind: "vulnerability"
aliases: ["CVE-2026-102612"]
title: "BACnet Stack: missing client certificate check lets anyone join the mesh"
severity: "high"
cvss: 8.1
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["bacnet", "bacnet-sc", "building-automation", "embedded", "linux", "package"]
not_affected_if: ["hub-not-used", "patched-version"]
published_at: "2026-11-13T19:17:37+00:00"
first_seen_at: "2026-11-13T19:52:09+00:00"
updated_at: "2026-11-13T19:54:04+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-102612", "first_seen_at": "2026-11-13T19:52:09+00:00"}]
exploit_sources: []
---

# BACnet Stack: missing client certificate check lets anyone join the mesh

Link for people: https://infrastack.ai/live/CVE-2026-102612 (this .md is for agents)

BACnet Stack's Linux WebSocket hub loads a CA certificate but never requires clients to present one, so it accepts TLS connections from clients with no certificate. A network-reachable host can join the BACnet/SC mesh without credentials.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed BACnet Stack version against the fixed versions listed below.
- Look in `ports/linux/websocket-srv.c` for `LWS_SERVER_OPTION_REQUIRE_VALID_OPENSSL_CLIENT_CERT` in `bws_srv_start()`; if it is absent, the hub is affected.

## Fix

- BACnet Stack `1.4.6`, `1.5.2`, `1.6.1`, or `1.7.0`, matching the release line you run.

## Timeline

- 2026-11-13T19:52:09+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-102612

## Documents

- [advisory] Vendor advisory: github.com https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-92q2-p4vr-fvmp

## From the sources

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_srv_start() in ports/linux/websocket-srv.c builds the libwebsockets server context with a CA certificate loaded but never sets LWS_SERVER_OPTION_REQUIRE_VALID_OPENSSL_CLIENT_CERT, so the hub accepts TLS connections from clients presenting no certificate at all. Any network-reachable host can join the BACnet/SC mesh without credentials. This issue has been patched in versions 1.4.6, 1.5.2, 1.6.1, and 1.7.0.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_