CVE-2026-29795 stellar-xdr: `StringM::from_str` bypasses max length validation
- Published
- Updated
- Exploit status
- No public exploit known
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::<N>::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.
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| crates.io stellar-xdr(crates.io) | < 25.0.1 | 25.0.1 |
| stellar rs-stellar-xdr | = < 25.0.1 | No fix listed |
| crates.io stellar-xdr(crates.io) | <= 25.0.0 | No fix listed |
| stellar-xdr | < 25.0.1 | 25.0.1 |
References
- https://github.com/stellar/rs-stellar-xdr/security/advisories/GHSA-x57h-xx53-v53w mitigation patch vendor-advisory
- nvd.nist.gov third-party-advisory vendor-advisory
- https://github.com/stellar/rs-stellar-xdr/issues/499 issue-tracking
- https://github.com/stellar/rs-stellar-xdr/pull/500 issue-tracking patch
- https://github.com/stellar/rs-stellar-xdr/commit/1f840013c3e2fca0321fb844b048afa01d10dda6 patch
- github.com product
- github.com