Skip to content

← Public intelligence

crates.io package

plonky2

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.6crates.ioPublished

    Soundness issue with Plonky2 look up tables

    CVE-2025-24802 · GHSA-hj49-h7fq-px5h

    Affected
    • crates.io plonky2 >= 1.0.0, <= 1.0.0
    Fixed in
    1.0.1· Vendor fix available
    Issue
    Impact 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 happens to be divisible by 26). The cause of problem is that the LookupTableGate-s are padded with zeros. The fix is done by padding with an existing table pair, similarly to LookupGate. A workaround from the user side is to extend the table (by repeating some entries) so that its length becomes divisible by 26. Fortunately, the seemingly most common use case, namely, hash functions with table-based sbox-es, are not vulnerable: both Monolith's and Tip5/Tip4's s-box tables already map 0 to 0; more generally, forcing several (0,0) pairs inside such a hash function appears to be a too strong restriction to find an otherwise valid trace. A malicious prover exploiting this could cheat a circuit which statement is the following: - output x + f(x) for some private…

    Recommended action: Upgrade to 1.0.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →