{"answers":{"affected":"2 open source packages ship an affected version, including stellar-xdr. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-29795 in the wild and no public exploit code.","fix":"Upgrade stellar-xdr to 25.0.1 or later.","what":"CVE-2026-29795 is a medium-severity vulnerability in rs-stellar-xdr, published on 6 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-29795 and fix it if it is affected.\n\nWhat it is: CVE-2026-29795 is a medium-severity vulnerability in rs-stellar-xdr, published on 6 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-29795 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- stellar-xdr (crates.io): affected all versions; fixed in 25.0.1\n- stellar-xdr (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-29795/ (Markdown: https://insights.sbomify.com/CVE-2026-29795/index.md)","id":"CVE-2026-29795","markdown":"https://insights.sbomify.com/CVE-2026-29795/index.md","name":"CVE-2026-29795","record":{"aliases":["GHSA-x57h-xx53-v53w"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Stellar XDR library","requires_auth":"none","summary":"The stellar-xdr library fails to enforce maximum length limits on strings, allowing oversized data to bypass validation and potentially corrupt downstream logic.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"stellar-xdr","vendor":"stellar"}],"cvss":{"score":4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"stellar-xdr is a library and CLI containing types and functionality for working with Stellar XDR. Prior to version 25.0.1, StringM::from_str does not validate that the input length is within the declared maximum (MAX). Calling StringM::\u003cN\u003e::from_str(s) where s is longer than N bytes succeeds and returns an Ok value instead of Err(Error::LengthExceedsMax), producing a StringM that violates its length invariant. This affects any code that constructs StringM values from string input using FromStr (including str::parse), and relies on the type's maximum length constraint being enforced. An oversized StringM could propagate through serialization, validation, or other logic that assumes the invariant holds. This issue has been patched in version 25.0.1.","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":"stellar-xdr: `StringM::from_str` bypasses max length validation","id":"CVE-2026-29795","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"IGL-Technologies eParking.fi Missing Authentication for Critical Function","id":"CVE-2026-29796"},"packages":[{"ecosystem":"crates.io","fixed":["25.0.1"],"introduced":["0"],"last_affected":[],"package":"stellar-xdr","purl":null,"source":"GHSA-x57h-xx53-v53w"},{"ecosystem":"crates.io","fixed":["25.0.1"],"introduced":["0"],"last_affected":[],"package":"stellar-xdr","purl":"pkg:cargo/stellar-xdr","source":"GHSA-x57h-xx53-v53w"}],"prev":{"headline":"Vikunja has Rate-Limit Bypass for Unauthenticated Users via Spoofed Headers","id":"CVE-2026-29794"},"products":["rs-stellar-xdr"],"published":"2026-03-06","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":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-09","vendors":["stellar"]},"summary":"The stellar-xdr library fails to enforce maximum length limits on strings, allowing oversized data to bypass validation and potentially corrupt downstream logic.","url":"https://insights.sbomify.com/CVE-2026-29795/"}