<?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://cve.radiocsirt.org</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, 05 Oct 2026 12:53:13 +0000</lastBuildDate>
    <item>
      <title>cnvd-2021-52404</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2021-52404</link>
      <description>cnvd-2021-52404</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2021-52404</guid>
    </item>
    <item>
      <title>EUVD-2026-28108</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-28108</link>
      <description>EUVD-2026-28108</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-28108</guid>
    </item>
    <item>
      <title>fkie_cve-2021-32738</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-32738</link>
      <description>&lt;p&gt;js-stellar-sdk is a Javascript library for communicating with a Stellar Horizon server. The `Utils.readChallengeTx` function used in SEP-10 Stellar Web Authentication states in its function documentation that it reads and validates the challenge transaction including verifying that the `serverAccountID` has signed the transaction. In js-stellar-sdk before version 8.2.3, the function does not verify that the server has signed the transaction. Applications that also used `Utils.verifyChallengeTxThreshold` or `Utils.verifyChallengeTxSigners` to verify the signatures including the server signature on the challenge transaction are unaffected as those functions verify the server signed the transaction. Applications calling `Utils.readChallengeTx` should update to version 8.2.3, the first version with a patch for this vulnerability, to ensure that the challenge transaction is completely valid and signed by the server creating the challenge transaction.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;js-stellar-sdk is a Javascript library for communicating with a Stellar Horizon server. The `Utils.readChallengeTx` function used in SEP-10 Stellar Web Authentication states in its function documentation that it reads and validates the challenge transaction including verifying that the `serverAccountID` has signed the transaction. In js-stellar-sdk before version 8.2.3, the function does not verify that the server has signed the transaction. Applications that also used `Utils.verifyChallengeTxThreshold` or `Utils.verifyChallengeTxSigners` to verify the signatures including the server signature on the challenge transaction are unaffected as those functions verify the server signed the transaction. Applications calling `Utils.readChallengeTx` should update to version 8.2.3, the first version with a patch for this vulnerability, to ensure that the challenge transaction is completely valid and signed by the server creating the challenge transaction.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-32738</guid>
    </item>
    <item>
      <title>GHSA-6cgh-hjpw-q3gq — Utils.readChallengeTx does not verify the server account signature</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6cgh-hjpw-q3gq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: stellar-sdk&lt;/p&gt;
&lt;p&gt;The `Utils.readChallengeTx` function used in [SEP-10 Stellar Web Authentication](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md) states in its function documentation that it reads and validates the challenge transaction including verifying that the `serverAccountID` has signed the transaction. The function does not verify that the server has signed the transaction and has been fixed so that it does in v8.2.3.&lt;/p&gt;
&lt;p&gt;Applications that also used `Utils.verifyChallengeTxThreshold` or `Utils.verifyChallengeTxSigners` to verify the signatures including the server signature on the challenge transaction are unaffected as those functions verify the server signed the transaction.&lt;/p&gt;
&lt;p&gt;Applications calling `Utils.readChallengeTx` should update to v8.2.3 to ensure that the challenge transaction is completely valid and signed by the server creating the challenge transaction.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: stellar-sdk&lt;/p&gt;
&lt;p&gt;The `Utils.readChallengeTx` function used in [SEP-10 Stellar Web Authentication](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md) states in its function documentation that it reads and validates the challenge transaction including verifying that the `serverAccountID` has signed the transaction. The function does not verify that the server has signed the transaction and has been fixed so that it does in v8.2.3.&lt;/p&gt;
&lt;p&gt;Applications that also used `Utils.verifyChallengeTxThreshold` or `Utils.verifyChallengeTxSigners` to verify the signatures including the server signature on the challenge transaction are unaffected as those functions verify the server signed the transaction.&lt;/p&gt;
&lt;p&gt;Applications calling `Utils.readChallengeTx` should update to v8.2.3 to ensure that the challenge transaction is completely valid and signed by the server creating the challenge transaction.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6cgh-hjpw-q3gq</guid>
    </item>
    <item>
      <title>gsd-2021-32738</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-32738</link>
      <description>gsd-2021-32738</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-32738</guid>
    </item>
  </channel>
</rss>
