CVE-2024-34149VulnerabilityPublished 30 Apr 2024Updated 21 Nov 2024

CVE-2024-34149: bitcoin · n/a

Affects bitcoinSource CVE Database V5

Mentioned vulnerabilities

CVE-2023-50428

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubbitcoin/bitcoin`pkg:github/bitcoin/bitcoin`Other threats	Affected <=27.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should monitor official Bitcoin Core and Bitcoin Knots repositories and communications for patches addressing CVE-2024-34149 and apply updates promptly once available. In the interim, node operators can implement custom policy checks to limit tapscript sizes or reject oversized scripts at the application layer. Network-level controls such as rate limiting and transaction filtering can reduce exposure to malformed scripts. Participation in community discussions and consensus-building efforts is recommended to support timely and effective mitigation strategies. Operators should also audit their node configurations to ensure they are not accepting non-standard or oversized scripts inadvertently. Running nodes with the latest stable releases and enabling verbose logging can help detect anomalous script submissions. Backup and recovery plans should be reviewed to prepare for potential disruptions. Finally, organizations should educate their teams about the implications of tapscript vulnerabilities and maintain situational awareness of emerging threats in the Bitcoin ecosystem.

Description

In Bitcoin Core through 27.0 and Bitcoin Knots before 25.1.knots20231115, tapscript lacks a policy size limit check, a different issue than CVE-2023-50428. NOTE: some parties oppose this new limit check (for example, because they agree with the objective but disagree with the technical mechanism, or because they have a different objective).

Impact

The vulnerability could allow attackers to submit tapscripts that exceed expected size limits, potentially leading to resource exhaustion or bypassing certain validation policies. This can degrade node performance, cause denial of service, or introduce subtle transaction validation inconsistencies that undermine blockchain integrity. Confidentiality impacts are limited but possible if malformed scripts interfere with transaction processing or leak information through side channels. Integrity and availability impacts are more pronounced, as malicious scripts could disrupt consensus or transaction acceptance. Organizations running affected Bitcoin nodes, including exchanges, wallet providers, miners, and infrastructure services, may experience service disruptions or increased risk of transaction malleability or invalid transactions being accepted. While no exploits are known currently, the widespread use of Bitcoin Core and Bitcoin Knots means that the vulnerability has a broad attack surface. The debate over the policy limit check also indicates potential delays in mitigation adoption, prolonging exposure. Overall, the threat could undermine trust and reliability in Bitcoin transaction processing if exploited at scale.

References

github.com/bitcoin/bitcoin/pull/29769 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 03:08 UTC

Technical details

References

Community reviews

Related threats