CVE-2026-32129: Poseidon V1 variable-length input collision via implicit zero-padding
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.
References
- github.com/advisories/GHSA-g2p6-hh5v-7hfm
- github.com/stellar/rs-soroban-poseidon
- github.com/stellar/rs-soroban-poseidon/commit/ceb20d3593fc4a8a951a7e99d8fa2344f8250a8c
- github.com/stellar/rs-soroban-poseidon/pull/10
- github.com/stellar/rs-soroban-poseidon/releases/tag/v25.0.1
- github.com/stellar/rs-soroban-poseidon/security/advisories/GHSA-g2p6-hh5v-7hfm
- nvd.nist.gov/vuln/detail/CVE-2026-32129
Code Behaviors & Features
Detect and mitigate CVE-2026-32129 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →