CVE-2026-29795

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 91% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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::::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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

March 6, 2026

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Aug 2, 2026
Patch available. Sources: github_commit, github_pr, github.
github Patch Available

StringM::from_str bypasses max length validation · Advisory · stellar/rs-stellar-xdr · GitHub

https://github.com/stellar/rs-stellar-xdr/security/advisories/GHSA-x57h-xx53-v53w
github_pr

Fix StringM::from_str max length validation

Fix merged in stellar/rs-stellar-xdr PR #500 on 2026-02-26 — awaiting tagged release

https://github.com/stellar/rs-stellar-xdr/pull/500
generic

Bug: `StringM::from_str` bypasses max length validation · Issue #499 · stellar/rs-stellar-xdr · GitHub

https://github.com/stellar/rs-stellar-xdr/issues/499
github_commit

commit 1f840013c3e2 (stellar/rs-stellar-xdr)

Fix landed in stellar/rs-stellar-xdr commit 1f840013c3e2 — awaiting tagged release

https://github.com/stellar/rs-stellar-xdr/commit/1f840013c3e2fca0321fb844b048afa01d10dda6

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFixed inDependents
stellar-xdr—25.0.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 20:15 UTCEPSS rescore
  2. 2026-09-20 20:15 UTCEPSS rescore
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 19:27 UTCEPSS rescore
  5. 2026-09-17 19:30 UTCEPSS rescore
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-13 16:47 UTCEPSS rescore
  9. 2026-09-12 15:01 UTCEPSS rescore
  10. 2026-09-11 14:52 UTCEPSS rescore
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-04 05:06 UTCEPSS rescore
  17. 2026-09-02 23:29 UTCOSV refresh
  18. 2026-09-02 14:11 UTCEPSS rescore
  19. 2026-09-01 13:53 UTCEPSS rescore
  20. 2026-09-01 04:39 UTCEPSS rescore
  21. 2026-09-01 04:39 UTCEPSS rescore
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 01:22 UTCEPSS rescore
  24. 2026-08-28 21:41 UTCEPSS rescore
  25. 2026-08-27 14:25 UTCEPSS rescore
Show 41 more
  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 14:17 UTCEPSS rescore
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-19 17:03 UTCEPSS rescore
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 12:21 UTCEG score recompute
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 08:14 UTCEG score recompute
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-12 23:47 UTCEG score recompute
  18. 2026-08-12 13:50 UTCEPSS rescore
  19. 2026-08-11 22:33 UTCEG score recompute
  20. 2026-08-11 13:42 UTCEPSS rescore
  21. 2026-08-11 05:21 UTCEG score recompute
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-09 20:52 UTCEG score recompute
  24. 2026-08-09 13:46 UTCEPSS rescore
  25. 2026-08-09 07:54 UTCEG score recompute
  26. 2026-08-08 16:37 UTCEPSS rescore
  27. 2026-08-07 19:22 UTCEG score recompute
  28. 2026-08-06 20:24 UTCEG score recompute
  29. 2026-08-06 13:46 UTCEPSS rescore
  30. 2026-08-06 02:23 UTCEG score recompute
  31. 2026-08-05 19:17 UTCEPSS rescore
  32. 2026-08-04 15:10 UTCEPSS rescore
  33. 2026-08-04 01:51 UTCEG score recompute
  34. 2026-08-03 10:36 UTCEPSS rescore
  35. 2026-08-02 18:35 UTCEG score recompute
  36. 2026-08-02 02:26 UTCEPSS rescore
  37. 2026-08-01 04:16 UTCEPSS rescore
  38. 2026-07-30 16:27 UTCEPSS rescore
  39. 2026-07-30 01:30 UTCEPSS rescore
  40. 2026-07-28 15:36 UTCEPSS rescore
  41. 2026-07-27 13:49 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-29795?
CVE-2026-29795 is a high vulnerability published on March 6, 2026. stellar-xdr is a library and CLI containing types and functionality for working with Stellar XDR. Prior to version 25.0.1, StringM::fromstr does not validate that the input length is within the declared maximum (MAX). Calling StringM::<N>::fromstr(s) where s is longer than N bytes succeeds and…
When was CVE-2026-29795 disclosed?
CVE-2026-29795 was first published in the National Vulnerability Database on March 6, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-29795 actively exploited?
CVE-2026-29795 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.8% of all scored CVEs.
What is the CVSS score of CVE-2026-29795?
CVE-2026-29795 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-29795?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-29795, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-29795

Explore →

Is Your Infrastructure Affected by CVE-2026-29795?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs