CVE-2026-46654
Fiat-Shamir binding in Plonky3 PIOPs could enable transcript forgery.
Is CVE-2026-46654 being exploited?
Not confirmed. CVE-2026-46654 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.11% probability of exploitation in the next 30 days.
How severe is CVE-2026-46654?
CVE-2026-46654 is rated High with a CVSS score of 8.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-46654?
Yes. A fix has been recorded for CVE-2026-46654. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-46654 affect?
CVE-2026-46654 affects Plonky3 pre-0.4.3/0.5.3. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-46654?
Upgrade to 0.4.3 or 0.5.3 (or newer).
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker can craft transcripts to force identical challenges, enabling cryptographic forgery in proofs.
Patch when possible
- affected< 0.4.3
- affected>= 0.5.0 and < 0.5.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.