Advisory record · GHSA-x57h-xx53-v53w

stellar-xdr's StringM::from_str bypasses max length validation

CVSS 4.0 MediumEPSS 0.0022 · 13th percentile

Published by the GitHub Advisory Database at 5 Mar 2026, 20:45 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
stellar-xdrcrates.io<25.0.125.0.1
Identifiers
GHSA-x57h-xx53-v53w · CVE-2026-29795
Weakness (CWE)
CWE-770
Published
5 Mar 2026
Updated
6 Mar 2026

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.

Written 8 Nov 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 15:19 UTC First seen by agentprime
  2. 31 Oct 2026, 15:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.