CVE-2024-1651

CRITICALNVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2024-02-20. NVD baseline CVSS 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
10.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 34%CVSS: 10.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Torrentpier version 2.4.1 allows executing arbitrary commands on the server.

This is possible because the application is vulnerable to insecure deserialization.

CVSS v3
10.0
EG Score
10.0(medium)
EG Risk
76(Attend)
EG Risk 76/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity100% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
98.2%
KEV
Not listed

Published

February 20, 2024

Last Modified

February 12, 2025

Advisory Details (2)

Auto-updated Jul 18, 2026
Patch available.
generic

GitHub - torrentpier/torrentpier: 🐂 TorrentPier. Bull-powered BitTorrent tracker engine · GitHub

https://github.com/torrentpier/torrentpier
generic Patch Available

Torrentpier 2.4.1 - RCE | Fluid Attacks

https://fluidattacks.com/advisories/xavi/

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
composertorrentpier/torrentpier—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
torrentpier/torrentpier2.3.0.4-beta ... v2.4.1 (24 versions)——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:16 UTCEPSS rescore
  2. 2026-07-23 14:17 UTCEPSS rescore
  3. 2026-07-23 14:17 UTCEPSS rescore
  4. 2026-07-23 02:32 UTCEG score recompute
  5. 2026-07-22 23:19 UTCEG score recompute
  6. 2026-07-22 14:07 UTCEPSS rescore
  7. 2026-07-20 17:06 UTCEPSS rescore
  8. 2026-07-19 02:27 UTCEPSS rescore
  9. 2026-07-18 10:03 UTCEPSS rescore
  10. 2026-07-18 10:03 UTCEPSS rescore
  11. 2026-07-15 16:56 UTCEPSS rescore
  12. 2026-07-15 16:56 UTCEPSS rescore
  13. 2026-07-15 01:59 UTCEPSS rescore
  14. 2026-07-15 01:59 UTCEPSS rescore
  15. 2026-07-14 19:10 UTCOSV refresh
  16. 2026-07-13 22:28 UTCEPSS rescore
  17. 2026-07-13 06:11 UTCEPSS rescore
  18. 2026-07-13 06:11 UTCEPSS rescore
  19. 2026-07-12 05:45 UTCEPSS rescore
  20. 2026-07-12 05:45 UTCEPSS rescore
  21. 2026-07-11 08:26 UTCEPSS rescore
  22. 2026-07-09 19:09 UTCEPSS rescore
  23. 2026-07-08 15:13 UTCEPSS rescore
  24. 2026-07-06 16:26 UTCEPSS rescore
  25. 2026-07-05 02:29 UTCEPSS rescore
Show 56 more
  1. 2026-07-04 06:30 UTCEPSS rescore
  2. 2026-07-04 06:30 UTCEPSS rescore
  3. 2026-07-01 15:05 UTCEPSS rescore
  4. 2026-06-28 04:55 UTCEPSS rescore
  5. 2026-06-27 03:07 UTCEPSS rescore
  6. 2026-06-27 03:07 UTCEPSS rescore
  7. 2026-06-26 20:09 UTCOSV refresh
  8. 2026-06-25 13:48 UTCEPSS rescore
  9. 2026-06-24 14:04 UTCEPSS rescore
  10. 2026-06-24 14:04 UTCEPSS rescore
  11. 2026-06-23 21:32 UTCEPSS rescore
  12. 2026-06-23 21:31 UTCEPSS rescore
  13. 2026-06-21 14:55 UTCEPSS rescore
  14. 2026-06-21 14:55 UTCEPSS rescore
  15. 2026-06-21 01:58 UTCEPSS rescore
  16. 2026-06-21 01:58 UTCEPSS rescore
  17. 2026-06-18 17:51 UTCEPSS rescore
  18. 2026-06-17 17:52 UTCEPSS rescore
  19. 2026-06-17 17:51 UTCEPSS rescore
  20. 2026-06-16 17:51 UTCEPSS rescore
  21. 2026-06-16 17:51 UTCEPSS rescore
  22. 2026-06-15 17:47 UTCEPSS rescore
  23. 2026-06-12 23:11 UTCEPSS rescore
  24. 2026-06-12 23:11 UTCEPSS rescore
  25. 2026-06-10 22:17 UTCEPSS rescore
  26. 2026-06-10 22:17 UTCEPSS rescore
  27. 2026-06-10 13:21 UTCEPSS rescore
  28. 2026-06-10 13:21 UTCEPSS rescore
  29. 2026-06-09 06:00 UTCOSV refresh
  30. 2026-06-08 14:16 UTCEPSS rescore
  31. 2026-06-08 14:16 UTCEPSS rescore
  32. 2026-06-07 15:24 UTCEPSS rescore
  33. 2026-06-07 15:24 UTCEPSS rescore
  34. 2026-06-06 13:46 UTCEPSS rescore
  35. 2026-06-06 13:46 UTCEPSS rescore
  36. 2026-06-05 22:46 UTCEPSS rescore
  37. 2026-06-05 22:46 UTCEPSS rescore
  38. 2026-06-05 06:09 UTCEPSS rescore
  39. 2026-06-05 06:09 UTCEPSS rescore
  40. 2026-06-04 13:11 UTCEPSS rescore
  41. 2026-06-04 13:11 UTCEPSS rescore
  42. 2026-06-04 13:11 UTCEPSS rescore
  43. 2026-06-02 20:12 UTCEPSS rescore
  44. 2026-06-02 20:12 UTCEPSS rescore
  45. 2026-06-01 13:51 UTCEPSS rescore
  46. 2026-06-01 13:51 UTCEPSS rescore
  47. 2026-05-31 00:15 UTCEPSS rescore
  48. 2026-05-31 00:15 UTCEPSS rescore
  49. 2026-05-29 13:43 UTCEPSS rescore
  50. 2026-05-28 13:44 UTCEPSS rescore
  51. 2026-05-28 13:44 UTCEPSS rescore
  52. 2026-05-28 13:44 UTCEPSS rescore
  53. 2026-05-27 13:40 UTCEPSS rescore
  54. 2026-05-24 08:16 UTCEG score recompute
  55. 2026-05-24 08:16 UTCGHSA enrichment
  56. 2026-05-23 23:25 UTCOSV refresh

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoChy011121/CVE-2024-1651-exploit-RCE
    First seen Feb 29, 2024

    (Mirorring)

    Open source ↗
  • GitHub PoCsharpicx/CVE-2024-1651-PoC
    First seen Feb 23, 2024

    Torrentpier v2.4.1. CVE-2024-1651. Remote Code Execution (RCE). Exploit.

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-1651?
CVE-2024-1651 is a critical vulnerability published on February 20, 2024. Torrentpier version 2.4.1 allows executing arbitrary commands on the server. This is possible because the application is vulnerable to insecure deserialization.
When was CVE-2024-1651 disclosed?
CVE-2024-1651 was first published in the National Vulnerability Database on February 20, 2024, with the most recent update on February 12, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-1651 actively exploited?
CVE-2024-1651 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-1651?
CVE-2024-1651 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2024-1651?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-1651, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-1651

Explore →

Is Your Infrastructure Affected by CVE-2024-1651?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs