Stellar Xdr
Approved changes feed: RSS · Atom
cpe:2.3:a:stellar:stellar-xdr:*:*:*:*:*:rust:*:*
part: a version: * update: *
| Vendor | Stellar (dff36e83-32ab-5204-bc95-0196d9a0c32c) |
|---|---|
| Product | Stellar Xdr (a624fda0-fdee-5323-b1e0-f36b550bccbb) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | rust |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/stellar/stellar-xdr |
purl2cpe | 2026-06-01 10:16:39.778485 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-29795 |
vulnerable | 2026-06-08 07:55:16.311865 |
stellar-xdr: `StringM::from_str` bypasses max length validation
MEDIUM (4)
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.
Published: 2026-03-06T20:42:43.403Z
Updated: 2026-03-09T20:54:30.156Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.