CVE-2026-32129

Enriched by CISA Privilege Escalation
 

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.
https://nvd.nist.gov/vuln/detail/CVE-2026-32129

Categories

CWE-328 : Use of Weak Hash
The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack). Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.) Programmable Logic Controller (PLC) uses a protocol with a cryptographically insecure hashing algorithm for passwords. SHA-1 algorithm is not collision-resistant. DNS product uses a weak hash (CRC32 or SHA-1) of the query name, allowing attacker to forge responses by computing domain names with the same hash. blogging product uses MD5-based algorithm for passwords. forging of certificate signatures using SHA-1 collisions. mobile app for backup sends SHA-1 hash of password in cleartext. Hard-coded hashed values for username and password contained in client-side script, allowing brute-force offline attacks.

References


 

AFFECTED (from MITRE)


Vendor Product Versions
stellar rs-soroban-poseidon
  • < 25.0.1 [affected]
© 2022 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation.

CPE

cpe start end


REMEDIATION




EXPLOITS


Exploit-db.com

id description date
No known exploits

POC Github

Url
No known exploits

Other Nist (github, ...)

Url
No known exploits


CAPEC


Common Attack Pattern Enumerations and Classifications

id description severity
461 Web Services API Signature Forgery Leveraging Hash Function Extension Weakness
High
68 Subvert Code-signing Facilities
Very High


MITRE


Techniques

id description
T1553.002 Subvert Trust Controls:Code Signing
© 2022 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation.