<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-10T19:33:11.447541+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-290885</id>
    <title>EUVD-2026-290885</title>
    <updated>2026-10-10T19:33:11.500838+00:00</updated>
    <content>EUVD-2026-290885</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-290885"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-40093</id>
    <title>fkie_cve-2026-40093</title>
    <updated>2026-10-10T19:33:11.500876+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. In 1.3.0 and earlier, block timestamp validation enforces that timestamp &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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-40093"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-49xc-52mp-cc9j</id>
    <title>GHSA-49xc-52mp-cc9j — nimiq-blockchain is missing a wall-clock upper bound on block timestamps</title>
    <updated>2026-10-10T19:33:11.500914+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: nimiq-blockchain</p>
<p>### Impact</p>
<p>Block timestamp validation enforces that `timestamp &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.</p>
<p>### Patches
TBD</p>
<p>### Workarounds
No know workarounds.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-49xc-52mp-cc9j"/>
  </entry>
</feed>
