<?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>Sat, 03 Oct 2026 01:44:56 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-232636</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-232636</link>
      <description>EUVD-2026-232636</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-232636</guid>
    </item>
    <item>
      <title>fkie_cve-2022-36061</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-36061</link>
      <description>&lt;p&gt;Elrond go is the go implementation for the Elrond Network protocol. In versions prior to 1.3.35, read only calls between contracts can generate smart contracts results. For example, if contract A calls in read only mode contract B and the called function will make changes upon the contract&amp;#39;s B state, the state will be altered for contract B as if the call was not made in the read-only mode. This can lead to some effects not designed by the original smart contracts programmers. This issue was patched in version 1.3.35. There are no known workarounds.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Elrond go is the go implementation for the Elrond Network protocol. In versions prior to 1.3.35, read only calls between contracts can generate smart contracts results. For example, if contract A calls in read only mode contract B and the called function will make changes upon the contract&amp;#39;s B state, the state will be altered for contract B as if the call was not made in the read-only mode. This can lead to some effects not designed by the original smart contracts programmers. This issue was patched in version 1.3.35. There are no known workarounds.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-36061</guid>
    </item>
    <item>
      <title>GHSA-mv8x-668m-53fg — Elrond-go has improper initialization</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mv8x-668m-53fg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/ElrondNetwork/elrond-go&lt;/p&gt;
&lt;p&gt;### Impact
Read only calls between contracts can generate smart contracts results. For example, if contract A calls in read only mode contract B and the called function will make changes upon the contract&amp;#39;s B state, the state will be altered for contract B as if the call was not made in the read-only mode. This can lead to some effects not designed by the original smart contracts programmers.&lt;/p&gt;
&lt;p&gt;### Patches
Patch v1.3.35 or higher&lt;/p&gt;
&lt;p&gt;### Workarounds
No workaround&lt;/p&gt;
&lt;p&gt;### References
For future reference and understanding of this issue, anyone can check this integration test https://github.com/ElrondNetwork/elrond-go/blob/8e402fa6d7e91e779980122d3798b2bf50892945/integrationTests/vm/txsFee/asyncESDT_test.go#L452 that proves the fix and prevents a future code regression.&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory:
* Open an issue in elrond-go ([http://github.com/ElrondNetwork/elrond-go/issues](https://github.com/ElrondNetwork/elrond-go/issues))&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/ElrondNetwork/elrond-go&lt;/p&gt;
&lt;p&gt;### Impact
Read only calls between contracts can generate smart contracts results. For example, if contract A calls in read only mode contract B and the called function will make changes upon the contract&amp;#39;s B state, the state will be altered for contract B as if the call was not made in the read-only mode. This can lead to some effects not designed by the original smart contracts programmers.&lt;/p&gt;
&lt;p&gt;### Patches
Patch v1.3.35 or higher&lt;/p&gt;
&lt;p&gt;### Workarounds
No workaround&lt;/p&gt;
&lt;p&gt;### References
For future reference and understanding of this issue, anyone can check this integration test https://github.com/ElrondNetwork/elrond-go/blob/8e402fa6d7e91e779980122d3798b2bf50892945/integrationTests/vm/txsFee/asyncESDT_test.go#L452 that proves the fix and prevents a future code regression.&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory:
* Open an issue in elrond-go ([http://github.com/ElrondNetwork/elrond-go/issues](https://github.com/ElrondNetwork/elrond-go/issues))&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mv8x-668m-53fg</guid>
    </item>
    <item>
      <title>gsd-2022-36061</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-36061</link>
      <description>gsd-2022-36061</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-36061</guid>
    </item>
  </channel>
</rss>
