CVE-2016-10725

N/A
Published: July 5, 2018 at 10:00 PM UTC
Updated: June 17, 2026 at 12:40 AM UTC
3 products affected across 1 vendorBitcoin CoreBitcoin QtBitcoind

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 0.13.0
Affected range stops below 0.13.0, so it looks safe — our inference, not a vendor statement
v < 0.13.0
Affected range stops below 0.13.0, so it looks safe — our inference, not a vendor statement
v < 0.13.0
Affected range stops below 0.13.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

Confidentiality
NONE
Integrity
NONE
Availability
PARTIAL
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-310

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card