CVE-2026-46654

HIGHPre-NVD 8.98.9—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% 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, secondary
8.9
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.9Exploit: NoneExposed: 0

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

Plonky3 is a toolkit for polynomial IOPs (PIOPs). Prior to versions 0.4.3 and 0.5.3, an attacker controlling prover-side observations can craft distinct transcripts that produce identical challenges, breaking the binding property of Fiat-Shamir. This issue has been patched in versions 0.4.3 and 0.5.3.

CVSS v3
8.9
EG Score
8.9(medium)
EG Risk
—
EPSS
1.4%
KEV
Not listed

Published

May 21, 2026

Last Modified

June 11, 2026

Advisory Details (1)

Auto-updated Jun 11, 2026
Patch available. Sources: github.
github Patch Available

MultiField32Challenger: transcript malleability and challenge entropy loss · Advisory · Plonky3/Plonky3 · GitHub

https://github.com/Plonky3/Plonky3/security/advisories/GHSA-vj64-rjf3-w3v7

Vendor Advisories for CVE-2026-46654(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFixed inDependents
p3-challenger—0.5.3—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 6× 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.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-20 17:08 UTCEPSS rescore
  3. 2026-07-19 14:31 UTCEPSS rescore
  4. 2026-07-18 10:04 UTCEPSS rescore
  5. 2026-07-17 21:59 UTCOSV refresh
  6. 2026-07-16 17:03 UTCEPSS rescore
  7. 2026-07-15 16:57 UTCEPSS rescore
  8. 2026-07-15 02:00 UTCEPSS rescore
  9. 2026-07-13 22:30 UTCEPSS rescore
  10. 2026-07-12 05:46 UTCEPSS rescore
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-07 13:46 UTCEPSS rescore
  14. 2026-07-06 02:23 UTCEPSS rescore
  15. 2026-07-05 02:30 UTCEPSS rescore
  16. 2026-07-04 06:31 UTCEPSS rescore
  17. 2026-07-01 15:07 UTCEPSS rescore
  18. 2026-06-30 23:22 UTCEPSS rescore
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-28 14:07 UTCEPSS rescore
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-27 03:08 UTCEPSS rescore
  25. 2026-06-23 21:33 UTCEPSS rescore
Show 17 more
  1. 2026-06-23 21:33 UTCEPSS rescore
  2. 2026-06-21 01:59 UTCEPSS rescore
  3. 2026-06-21 01:59 UTCEPSS rescore
  4. 2026-06-19 19:26 UTCEPSS rescore
  5. 2026-06-19 19:26 UTCEPSS rescore
  6. 2026-06-18 17:52 UTCEPSS rescore
  7. 2026-06-18 17:52 UTCEPSS rescore
  8. 2026-06-17 17:53 UTCEPSS rescore
  9. 2026-06-16 17:53 UTCEPSS rescore
  10. 2026-06-15 17:49 UTCEPSS rescore
  11. 2026-06-13 23:00 UTCEPSS rescore
  12. 2026-06-12 23:12 UTCEPSS rescore
  13. 2026-06-12 23:12 UTCEPSS rescore
  14. 2026-06-11 14:00 UTCEPSS rescore
  15. 2026-06-10 23:01 UTCEG score recompute▲ 8.90
  16. 2026-06-10 23:00 UTCNVD updateCVSS v3 → 8.9 · CVSS v4 → 8.9
  17. 2026-05-24 06:11 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-46654?
CVE-2026-46654 is a high vulnerability published on May 21, 2026. Plonky3 is a toolkit for polynomial IOPs (PIOPs). Prior to versions 0.4.3 and 0.5.3, an attacker controlling prover-side observations can craft distinct transcripts that produce identical challenges, breaking the binding property of Fiat-Shamir. This issue has been patched in versions 0.4.3 and…
When was CVE-2026-46654 disclosed?
CVE-2026-46654 was first published in the National Vulnerability Database on May 21, 2026, with the most recent update on June 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46654 actively exploited?
CVE-2026-46654 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46654?
CVE-2026-46654 has a CVSS v3 base score of 8.9 (NVD).
How do I remediate CVE-2026-46654?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46654, 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-2026-46654

Explore →

Is Your Infrastructure Affected by CVE-2026-46654?

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

Start Free Scan →Browse All CVEs