CVE-2026-32129
HIGHsoroban-poseidon < 25.0.1 - Hash Collision via Implicit Zero-Filling in PoseidonSponge
Title source: llmDescription
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.
References (3)
Core 3
Core References
Vendor Advisory x_refsource_confirm
https://github.com/stellar/rs-soroban-poseidon/security/advisories/GHSA-g2p6-hh5v-7hfm
Issue Tracking x_refsource_misc
https://github.com/stellar/rs-soroban-poseidon/pull/10
Release Notes x_refsource_misc
https://github.com/stellar/rs-soroban-poseidon/releases/tag/v25.0.1
Scores
CVSS v4
8.7
EPSS
0.0022
EPSS Percentile
12.4%
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
CISA SSVC
Vulnrichment
Exploitation
none
Automatable
yes
Technical Impact
partial
Details
CWE
CWE-328
Status
published
Products (1)
crates.io/soroban-poseidon
0 - 25.0.1crates.io
Published
Mar 12, 2026
Tracked Since
Mar 13, 2026