{"answers":{"affected":"2 open source packages ship an affected version, including soroban-poseidon.","exploited":"There is no known exploitation of CVE-2026-32129 in the wild and no public exploit code.","fix":"Upgrade soroban-poseidon to 25.0.1 or later.","what":"CVE-2026-32129 is a high-severity vulnerability in stellar rs-soroban-poseidon, published on 12 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-32129 and fix it if it is affected.\n\nWhat it is: CVE-2026-32129 is a high-severity vulnerability in stellar rs-soroban-poseidon, published on 12 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-32129 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- soroban-poseidon (crates.io): affected all versions; fixed in 25.0.1\n- soroban-poseidon (crates.io): affected all versions; fixed in 25.0.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-32129/ (Markdown: https://insights.sbomify.com/CVE-2026-32129/index.md)","id":"CVE-2026-32129","markdown":"https://insights.sbomify.com/CVE-2026-32129/index.md","name":"CVE-2026-32129","record":{"aliases":["GHSA-g2p6-hh5v-7hfm"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust cryptographic library","requires_auth":"none","summary":"Attackers can create trivial hash collisions in Poseidon V1 due to implicit zero-padding, compromising integrity for smart contract developers using this library.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-328","name":"Use of Weak Hash"}],"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() \u003c 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 \u003e 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.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Poseidon V1 variable-length input collision via implicit zero-padding","id":"CVE-2026-32129","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"ZITADEL SCIM Authentication Bypass via URL Encoding","id":"CVE-2026-32130"},"packages":[{"ecosystem":"crates.io","fixed":["25.0.1"],"introduced":["0"],"last_affected":[],"package":"soroban-poseidon","purl":null,"source":"GHSA-g2p6-hh5v-7hfm"},{"ecosystem":"crates.io","fixed":["25.0.1"],"introduced":["0"],"last_affected":[],"package":"soroban-poseidon","purl":"pkg:cargo/soroban-poseidon","source":"GHSA-g2p6-hh5v-7hfm"}],"prev":{"headline":"FastGPT Python Sandbox Bypass of File-Write Restriction","id":"CVE-2026-32128"},"products":["rs-soroban-poseidon"],"published":"2026-03-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-13","vendors":["stellar"]},"summary":"Attackers can create trivial hash collisions in Poseidon V1 due to implicit zero-padding, compromising integrity for smart contract developers using this library.","url":"https://insights.sbomify.com/CVE-2026-32129/"}