CVE-2024-34478: btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it

Q: How do I fix CVE-2024-34478?

btcd: upgrade to 0.24.0. Exact commands for each OS are on this page.

Q: Is CVE-2024-34478 being exploited?

CVE-2024-34478 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-34478 affect?

CVE-2024-34478 affects btcd. Severity is high (CVSS 7.5). btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be tre

Q: How urgent is CVE-2024-34478?

Priority 43/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2024-34478 is a high-severity flaw (CVSS 7.5) affecting btcd. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be treated as unsigned. There can be a chain split and loss of funds.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 54%)
CISA exploited list	No
Weakness	CWE-436
Published	2024-05-05
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: btcd project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-05-05 01:15 UTCPublished CVE record published
2026-06-17 07:33 UTCUpdated Record last modified

btcd project btcd UPGRADE

Affected: < 0.24.0

Fixed in: 0.24.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy btcd || rpm -q btcd || btcd --version

2. UPGRADE to 0.24.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade btcd

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade btcd

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-34478?

btcd: upgrade to 0.24.0. Exact commands for each OS are on this page.

Is CVE-2024-34478 being exploited?

CVE-2024-34478 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-34478 affect?

CVE-2024-34478 affects btcd. Severity is high (CVSS 7.5). btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be tre

How urgent is CVE-2024-34478?

Priority 43/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2024-38365 HIGH 7.4 UPGRADE btcd is an alternative full node bitcoin implementation written in Go (golang)

References

← Back to latest CVEs