Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The stellar-xdr crate, versions before 25.0.1, has a flaw where StringM::from_str accepts input longer than the type's declared maximum length and returns Ok instead of an error. An attacker who can supply string input to code that parses it into StringM can produce a value that breaks the length invariant, which may then affect serialization or validation logic. Upgrade to stellar-xdr 25.0.1 or later. Until then, check the byte length of input before calling from_str, or use StringM::try_from on the bytes instead.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 4.0 | Medium | 3.1 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0022, the 13th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:19 UTC First seen by agentprime
- 31 Oct 2026, 15:19 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-x57h-xx53-v53w
- OSV: GHSA-x57h-xx53-v53w
- github.com/stellar/rs-stellar-xdr/security/advisories/GHSA-x57h-xx53-v53w
- nvd.nist.gov/vuln/detail/CVE-2026-29795
- github.com/stellar/rs-stellar-xdr/issues/499
- github.com/stellar/rs-stellar-xdr/pull/500
- github.com/stellar/rs-stellar-xdr/commit/1f840013c3e2fca0321fb844b048afa01d10dda6
- github.com/stellar/rs-stellar-xdr