Skip to main content
CVE Radar
highDenial of Servicepublic exploit

CVE-2026-100403

CVE-2026-100403 — BACnet Stack: BACnet/SC hub grows its WebSocket reassembly buffer without limit, so a peer can exhaust its memory

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, the BACnet/SC hub's Linux WebSocket server reassembles fragmented WebSocket messages into a per-connection fragment_buffer. It grows that buffer with realloc() on every non-final frame, with no upper bound. A peer that streams binary continuation fragments and never sets FIN keeps the hub reallocating until the box runs out of memory or the process is OOM-killed. The buffer starts at the maximum legal BVLC-SC NPDU size, but nothing after that ties its growth back to that limit. This issue has been patched in versions 1.4.6, 1.5.2, 1.6.1, and 1.7.0.

Published Updated Sources: bacnet-stack (CNA), GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Reported

not confirmed by CISA

EPSS

0%

ahead of 0% of scored CVEs

Affects

Bacnet-Stack

3 products listed

CVSS base

7.5

high

Remediation

The vendor's own words where we have them.

Upgrade Bacnet-stack to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Prioritize based on EPSS, PoC availability, and external exposure.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Affected vendors, products and versions
VendorProductVersionsStatus
Bacnet-Stackbacnet-stack< 1.4.6Vulnerable
Bacnet-Stackbacnet-stack>= 1.5.0, < 1.5.2Vulnerable
Bacnet-Stackbacnet-stack>= 1.6.0, < 1.6.1Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

None

Integrity

None

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Every CVSS base score collected, by source and version
ScoreVersionSeverityExpl.ImpactSource
7.5CVSS 3.1highn/an/abacnet-stack (CNA)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Weakness & attack patterns

  • CWE-400Uncontrolled Resource Consumption

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-147 · XML Ping of the DeathCAPEC-492 · Regular Expression Exponential BlowupCAPEC-197 · XML Entity Expansion
  • T1499Endpoint Denial of Service

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

PoC repos

4

1 of the 4 sampled are weaponized

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /SC.
  • Prioritize edge telemetry for network-reachable Bacnet-stack.
  • Monitor for scanner or exploit-pattern traffic after 4 public PoC repositories were reported.
web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Added · CVSS 3.1 7.5 (AV:N)

    Nov 13, 2026 · NVD

  3. Initial · CVE published

    Nov 13, 2026 · NVD

  4. CVE published by NIST.

    Nov 13, 2026 · SOCRadar CTI

References

2 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-100403 is BACnet Stack: BACnet/SC hub grows its WebSocket reassembly buffer without limit, so a peer can exhaust its memory, a high vulnerability affecting Bacnet-stack from Bacnet-stack. The current evidence does not list it in CISA KEV, and the exploit status is: Exploitation is reported, but no independent confirmation is available in the sources we have. Public exploit evidence is: 4 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.5 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.