<?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, 10 Oct 2026 18:27:22 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-290885</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-290885</link>
      <description>EUVD-2026-290885</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-290885</guid>
    </item>
    <item>
      <title>fkie_cve-2026-40093</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-40093</link>
      <description>&lt;p&gt;nimiq-blockchain provides persistent block storage for Nimiq&amp;#39;s Rust implementation. In 1.3.0 and earlier, block timestamp validation enforces that timestamp &amp;gt;= parent.timestamp for non-skip blocks and timestamp == parent.timestamp + MIN_PRODUCER_TIMEOUT for skip blocks, but there is no visible upper bound check against the wall clock. A malicious block-producing validator can set block timestamps arbitrarily far in the future. This directly affects reward calculations via Policy::supply_at() and batch_delay() in blockchain/src/reward.rs, inflating the monetary supply beyond the intended emission schedule.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;nimiq-blockchain provides persistent block storage for Nimiq&amp;#39;s Rust implementation. In 1.3.0 and earlier, block timestamp validation enforces that timestamp &amp;gt;= parent.timestamp for non-skip blocks and timestamp == parent.timestamp + MIN_PRODUCER_TIMEOUT for skip blocks, but there is no visible upper bound check against the wall clock. A malicious block-producing validator can set block timestamps arbitrarily far in the future. This directly affects reward calculations via Policy::supply_at() and batch_delay() in blockchain/src/reward.rs, inflating the monetary supply beyond the intended emission schedule.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-40093</guid>
    </item>
    <item>
      <title>GHSA-49xc-52mp-cc9j — nimiq-blockchain is missing a wall-clock upper bound on block timestamps</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-49xc-52mp-cc9j</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: nimiq-blockchain&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Block timestamp validation enforces that `timestamp &amp;gt;= parent.timestamp` for non-skip blocks and `timestamp == parent.timestamp + MIN_PRODUCER_TIMEOUT` for skip blocks, but there is no visible upper bound check against the wall clock. A malicious block-producing validator can set block timestamps arbitrarily far in the future. This directly affects reward calculations via `Policy::supply_at()` and `batch_delay()` in `blockchain/src/reward.rs`, inflating the monetary supply beyond the intended emission schedule.&lt;/p&gt;
&lt;p&gt;### Patches
TBD&lt;/p&gt;
&lt;p&gt;### Workarounds
No know workarounds.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: nimiq-blockchain&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Block timestamp validation enforces that `timestamp &amp;gt;= parent.timestamp` for non-skip blocks and `timestamp == parent.timestamp + MIN_PRODUCER_TIMEOUT` for skip blocks, but there is no visible upper bound check against the wall clock. A malicious block-producing validator can set block timestamps arbitrarily far in the future. This directly affects reward calculations via `Policy::supply_at()` and `batch_delay()` in `blockchain/src/reward.rs`, inflating the monetary supply beyond the intended emission schedule.&lt;/p&gt;
&lt;p&gt;### Patches
TBD&lt;/p&gt;
&lt;p&gt;### Workarounds
No know workarounds.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-49xc-52mp-cc9j</guid>
    </item>
  </channel>
</rss>
