soroban-poseidon
Affected
- introduced
0, fixed25.0.1(semver)
Fixed versions
25.0.1
Fix
- Fixed version
25.0.1cargo update -p soroban-poseidon --precise 25.0.1
Advisory
Also known as: CVE-2026-32129
Poseidon V1 variable-length input collision via implicit zero-padding
Impact
Poseidon V1 (PoseidonSponge) accepts variable-length inputs without injective padding. When a caller provides fewer inputs than the sponge rate (inputs.len() < T - 1), unused rate positions are implicitly zero-filled. This allows trivial hash collisions: for any input vector [m1, ..., mk] hashed with a sponge of rate > k, hash([m1, ..., mk]) equals hash([m1, ..., mk, 0]) because both produce identical pre-permutation states.
This affects any use of PoseidonSponge or poseidon_hash where the number of inputs is less than T - 1 (e.g., hashing 1 input with T=3).
Poseidon2 (Poseidon2Sponge) is not affected — it encodes the input length in the capacity element (IV = input_len << 64), making different-length inputs produce distinct states.
Patches
Fixed by enforcing inputs.len() == RATE in PoseidonSponge::compute_hash, matching circom's invariant that nInputs always equals T - 1. Users should upgrade to the next release containing this fix.
Workarounds
If upgrading is not immediately possible:
T = inputs.len() + 1 (full-rate), which is how circom uses Poseidon. For example, to hash 2 inputs, use T=3; to hash 1 input, use T=2. Never use a sponge with more rate capacity than the number of inputs.Poseidon2Sponge, which is safe for variable-length inputs due to its length-encoding IV.References
nInputs determines THigh Basis: The source's own band: HIGH
0, fixed 25.0.1 (semver)25.0.1
25.0.1cargo update -p soroban-poseidon --precise 25.0.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0