<?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-03T18:14:05.842836+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-342833</id>
    <title>EUVD-2026-342833</title>
    <updated>2026-10-03T18:14:05.949757+00:00</updated>
    <content>EUVD-2026-342833</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-342833"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-65058</id>
    <title>fkie_cve-2026-65058</title>
    <updated>2026-10-03T18:14:05.949806+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Trezor Safe 3, Safe 5, and Safe 7 firmware contains a confirmation-binding flaw in the Ethereum sign_tx / sign_tx_eip1559 flow. For contract interactions, the device confirms only the initial calldata chunk while the signature commits to the full streamed calldata. An attacker could present calldata to a victim then supply a different tail that changes the signed transaction. Fixed in 70c9b0c.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-65058"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-6552-m3hr-mqwj</id>
    <title>GHSA-6552-m3hr-mqwj</title>
    <updated>2026-10-03T18:14:05.949863+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Trezor Safe 3, Safe 5, and Safe 7 firmware contains a confirmation-binding flaw in the Ethereum sign_tx / sign_tx_eip1559 flow. For contract interactions, the device confirms only the initial calldata chunk while the signature commits to the full streamed calldata. An attacker could present calldata to a victim then supply a different tail that changes the signed transaction. Fixed in 70c9b0c.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-6552-m3hr-mqwj"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/va-26-202-02</id>
    <title>VA-26-202-02 — Trezor Safe improper security check in on-device display</title>
    <updated>2026-10-03T18:14:05.949907+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Trezor Safe 3, Safe 5, and Safe 7 firmware contains a confirmation-binding flaw in the Ethereum sign_tx / sign_tx_eip1559 flow. For contract interactions, the device confirms only the initial calldata chunk while the signature commits to the full streamed calldata. An attacker could present calldata to a victim then supply a different tail that changes the signed transaction. Fixed in 70c9b0c.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/va-26-202-02"/>
  </entry>
</feed>
