CVE-2025-24802

HIGHNVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: None knownExposed: 0

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

Plonky2 is a SNARK implementation based on techniques from PLONK and FRI. Lookup tables, whose length is not divisible by 26 = floor(num_routed_wires / 3) always include the 0 -> 0 input-output pair. Thus a malicious prover can always prove that f(0) = 0 for any lookup table f (unless its length happens to be divisible by 26). The cause of problem is that the LookupTableGate-s are padded with zeros. A workaround from the user side is to extend the table (by repeating some entries) so that its length becomes divisible by 26. This vulnerability is fixed in 1.0.1.

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
54(Track)
EG Risk 54/100SSVC: Track

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
Severity86% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

January 30, 2025

Last Modified

April 15, 2026

Advisory Details (3)

Auto-updated Sep 2, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Soundness issue with Plonky2 look up tables · Advisory · 0xPolygonZero/plonky2 · GitHub

https://github.com/0xPolygonZero/plonky2/security/advisories/GHSA-hj49-h7fq-px5h
github_commit Patch Available

commit 091047f7f10c (0xPolygonZero/plonky2)

Patch available: 0xPolygonZero/plonky2 v1.0.1 (contains commit 091047f7f10c)

https://github.com/0xPolygonZero/plonky2/commit/091047f7f10cae082716f3738ad59a583835f7b6
generic

plonky2/plonky2/src/plonk/prover.rs at main · 0xPolygonZero/plonky2 · GitHub

https://github.com/0xPolygonZero/plonky2/blob/main/plonky2/src/plonk/prover.rs#L97

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFixed inDependents
plonky21.0.01.0.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 26× 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.

Showing the most recent 100 of 177 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-24802?
CVE-2025-24802 is a high vulnerability published on January 30, 2025. Plonky2 is a SNARK implementation based on techniques from PLONK and FRI. Lookup tables, whose length is not divisible by 26 = floor(numroutedwires / 3) always include the 0 -> 0 input-output pair. Thus a malicious prover can always prove that f(0) = 0 for any lookup table f (unless its length…
When was CVE-2025-24802 disclosed?
CVE-2025-24802 was first published in the National Vulnerability Database on January 30, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-24802 actively exploited?
CVE-2025-24802 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.7% of all scored CVEs.
What is the CVSS score of CVE-2025-24802?
CVE-2025-24802 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2025-24802?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-24802, 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-2025-24802

Explore →

Is Your Infrastructure Affected by CVE-2025-24802?

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

Start Free Scan →Browse All CVEs