<?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>Fri, 02 Oct 2026 23:51:52 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-213835</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-213835</link>
      <description>EUVD-2026-213835</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-213835</guid>
    </item>
    <item>
      <title>fkie_cve-2023-30541</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-30541</link>
      <description>&lt;p&gt;OpenZeppelin Contracts is a library for secure smart contract development. A function in the implementation contract may be inaccessible if its selector clashes with one of the proxy&amp;#39;s own selectors. Specifically, if the clashing function has a different signature with incompatible ABI encoding, the proxy could revert while attempting to decode the arguments from calldata. The probability of an accidental clash is negligible, but one could be caused deliberately and could cause a reduction in availability. The issue has been fixed in version 4.8.3. As a workaround if a function appears to be inaccessible for this reason, it may be possible to craft the calldata such that ABI decoding does not fail at the proxy and the function is properly proxied through.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenZeppelin Contracts is a library for secure smart contract development. A function in the implementation contract may be inaccessible if its selector clashes with one of the proxy&amp;#39;s own selectors. Specifically, if the clashing function has a different signature with incompatible ABI encoding, the proxy could revert while attempting to decode the arguments from calldata. The probability of an accidental clash is negligible, but one could be caused deliberately and could cause a reduction in availability. The issue has been fixed in version 4.8.3. As a workaround if a function appears to be inaccessible for this reason, it may be possible to craft the calldata such that ABI decoding does not fail at the proxy and the function is properly proxied through.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-30541</guid>
    </item>
    <item>
      <title>GHSA-mx2q-35m2-x2rh — OpenZeppelin Contracts TransparentUpgradeableProxy clashing selector calls may not be delegated</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mx2q-35m2-x2rh</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @openzeppelin/contracts, npm: @openzeppelin/contracts-upgradeable&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A function in the implementation contract may be inaccessible if its selector clashes with one of the proxy&amp;#39;s own selectors. Specifically, if the clashing function has a different signature with incompatible ABI encoding, the proxy could revert while attempting to decode the arguments from calldata.&lt;/p&gt;
&lt;p&gt;The probability of an accidental clash is negligible, but one could be caused deliberately.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue has been fixed in v4.8.3.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If a function appears to be inaccessible for this reason, it may be possible to craft the calldata such that ABI decoding does not fail at the proxy and the function is properly proxied through.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;https://github.com/OpenZeppelin/openzeppelin-contracts/pull/4154&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @openzeppelin/contracts, npm: @openzeppelin/contracts-upgradeable&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A function in the implementation contract may be inaccessible if its selector clashes with one of the proxy&amp;#39;s own selectors. Specifically, if the clashing function has a different signature with incompatible ABI encoding, the proxy could revert while attempting to decode the arguments from calldata.&lt;/p&gt;
&lt;p&gt;The probability of an accidental clash is negligible, but one could be caused deliberately.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue has been fixed in v4.8.3.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If a function appears to be inaccessible for this reason, it may be possible to craft the calldata such that ABI decoding does not fail at the proxy and the function is properly proxied through.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;https://github.com/OpenZeppelin/openzeppelin-contracts/pull/4154&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mx2q-35m2-x2rh</guid>
    </item>
    <item>
      <title>gsd-2023-30541</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-30541</link>
      <description>gsd-2023-30541</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-30541</guid>
    </item>
  </channel>
</rss>
