Data integrity violation via unchecked string length
Published Mar 6, 2026 · Updated Mar 6, 2026
Improper length validation in stellar-xdr before 25.0.1 allows local users to create oversized StringM values through string parsing. StringM::from_str wraps unescaped input bytes directly in StringM instead of routing them through the length-checking TryFrom conversion. Exploitation requires code to parse attacker-influenced strings and trust the declared maximum; the resulting value can violate downstream serialization or validation assumptions.
Summary
What happened
Improper length validation in stellar-xdr before 25.0.1 allows local users to create oversized StringM values through string parsing. StringM::from_str wraps unescaped input bytes directly in StringM instead of routing them through the length-checking TryFrom conversion. Exploitation requires code to parse attacker-influenced strings and trust the declared maximum; the resulting value can violate downstream serialization or validation assumptions.
The record
- CVE
- CVE-2026-29795
- Published
- Mar 6, 2026
- Updated
- Mar 6, 2026
- Vendor
- Stellar Development Foundation
- Product
- stellar-xdr
- Classifications
- CWE-770
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 6, 2026CVE publishedPublication date reported by the CVE source.
- Mar 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 25.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo