<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 28 Sep 2026 10:46:31 +0000</lastBuildDate>
    <item>
      <title>BREW-stellar-xdr-CVE-2026-29795 — stellar-xdr: `StringM::from_str` bypasses max length validation</title>
      <link>https://vulnerability.circl.lu/vuln/brew-stellar-xdr-cve-2026-29795</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: stellar-xdr&lt;/p&gt;
&lt;p&gt;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::&amp;lt;N&amp;gt;::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&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: stellar-xdr&lt;/p&gt;
&lt;p&gt;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::&amp;lt;N&amp;gt;::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&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/brew-stellar-xdr-cve-2026-29795</guid>
    </item>
    <item>
      <title>fkie_cve-2026-29795</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-29795</link>
      <description>&lt;p&gt;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::&amp;lt;N&amp;gt;::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&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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::&amp;lt;N&amp;gt;::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&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-29795</guid>
    </item>
    <item>
      <title>GHSA-x57h-xx53-v53w — stellar-xdr's StringM::from_str bypasses max length validation</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-x57h-xx53-v53w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: stellar-xdr&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;`StringM::from_str` does not validate that the input length is within the declared maximum (`MAX`). Calling `StringM::&amp;lt;N&amp;gt;::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.&lt;/p&gt;
&lt;p&gt;This affects any code that constructs `StringM` values from string input using `FromStr` (including `str::parse`), and relies on the type&amp;#39;s maximum length constraint being enforced. An oversized `StringM` could propagate through serialization, validation, or other logic that assumes the invariant holds.&lt;/p&gt;
&lt;p&gt;All published versions of the `stellar-xdr` crate up to and including `v25.0.0` are affected.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The fix is merged in [#500](https://github.com/stellar/rs-stellar-xdr/pull/500). It replaces the direct `Ok(Self(b))` construction with `b.try_into()`, which routes through `TryFrom&amp;lt;Vec&amp;lt;u8&amp;gt;&amp;gt;` and properly validates the length — matching the pattern already used by `BytesM::from_str`.&lt;/p&gt;
&lt;p&gt;Users should upgrade to the first release containing this fix once published (the next release after `v25.0.0`).&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Validate the byte length of string input before calling `StringM::from_str`, or construct `StringM` values via `StringM::try_from(s.as_bytes().to_vec())` which correctly enforces the length constraint.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;- Issue: https://github.com/stellar/rs-stellar-xdr/issues/499
- Fix: https://github.com/stellar/rs-stellar-xdr/pull/500&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: stellar-xdr&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;`StringM::from_str` does not validate that the input length is within the declared maximum (`MAX`). Calling `StringM::&amp;lt;N&amp;gt;::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.&lt;/p&gt;
&lt;p&gt;This affects any code that constructs `StringM` values from string input using `FromStr` (including `str::parse`), and relies on the type&amp;#39;s maximum length constraint being enforced. An oversized `StringM` could propagate through serialization, validation, or other logic that assumes the invariant holds.&lt;/p&gt;
&lt;p&gt;All published versions of the `stellar-xdr` crate up to and including `v25.0.0` are affected.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The fix is merged in [#500](https://github.com/stellar/rs-stellar-xdr/pull/500). It replaces the direct `Ok(Self(b))` construction with `b.try_into()`, which routes through `TryFrom&amp;lt;Vec&amp;lt;u8&amp;gt;&amp;gt;` and properly validates the length — matching the pattern already used by `BytesM::from_str`.&lt;/p&gt;
&lt;p&gt;Users should upgrade to the first release containing this fix once published (the next release after `v25.0.0`).&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Validate the byte length of string input before calling `StringM::from_str`, or construct `StringM` values via `StringM::try_from(s.as_bytes().to_vec())` which correctly enforces the length constraint.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;- Issue: https://github.com/stellar/rs-stellar-xdr/issues/499
- Fix: https://github.com/stellar/rs-stellar-xdr/pull/500&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-x57h-xx53-v53w</guid>
    </item>
  </channel>
</rss>
