CVE-2026-32129 Poseidon V1 variable-length input collision via implicit zero-padding
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: yes · technical impact: partial
Description
soroban-poseidon provides Poseidon and Poseidon2 cryptographic hash functions for Soroban smart contracts. 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.
Upgrade path
2 packages: 1 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| crates.io soroban-poseidon(crates.io) | < 25.0.1 | 25.0.1 | Fixed |
| stellar rs-soroban-poseidon | = < 25.0.1 | No fix listed | Versions listed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| crates.io soroban-poseidon(crates.io) | < 25.0.1 | 25.0.1 |
| stellar rs-soroban-poseidon | = < 25.0.1 | No fix listed |
References
- https://github.com/stellar/rs-soroban-poseidon/security/advisories/GHSA-g2p6-hh5v-7hfm vendor-advisory
- nvd.nist.gov third-party-advisory vendor-advisory
- https://github.com/stellar/rs-soroban-poseidon/pull/10 patch
- github.com patch
- github.com product
- https://github.com/stellar/rs-soroban-poseidon/releases/tag/v25.0.1
- github.com