Skip to content
Connect AISign inSign up free
CVE-2026-297954.0MediumCWE-770

CVE-2026-29795: stellar-xdr: `StringM::from_str` bypasses max length validation

stellar · rs-stellar-xdr

Affected: stellar rs-stellar-xdr · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.2%probability of exploitation in the next 30 days
13th percentile
050100

Higher than 13% of scored CVEs

4.0MediumCVSS 3.1
LowMedium

DescriptionCVE.org

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 products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • stellar · rs-stellar-xdr< 25.0.1

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
stellar
Published
March 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-29795 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References