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) because ...

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.

Metrics

EPSS Probability

2.50%

82.7th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-310

Affected Software

Vendor	Product	Versions
Bitcoin	Bitcoin Core	< 0.13.0
Bitcoin	Bitcoin-Qt	< 0.13.0
Bitcoin	Bitcoind	< 0.13.0

References

Timeline

Published: Jul 5, 2018
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is 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) 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.

How severe is CVE-2016-10725?

Severity scoring for CVE-2016-10725 is pending analysis. The EPSS model estimates a 2.50% probability of exploitation in the next 30 days.

How do I fix CVE-2016-10725?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.