<?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 22:02:55 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-231888</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-231888</link>
      <description>EUVD-2026-231888</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-231888</guid>
    </item>
    <item>
      <title>fkie_cve-2022-23507</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-23507</link>
      <description>&lt;p&gt;Tendermint is a high-performance blockchain consensus engine for Byzantine fault tolerant applications. Versions prior to 0.28.0 contain a potential attack via Improper Verification of Cryptographic Signature, affecting anyone using the tendermint-light-client and related packages to perform light client verification (e.g. IBC-rs, Hermes). The light client does not check that the chain IDs of the trusted and untrusted headers match, resulting in a possible attack vector where someone who finds a header from an untrusted chain that satisfies all other verification conditions (e.g. enough overlapping validator signatures) could fool a light client. The attack vector is currently theoretical, and no proof-of-concept exists yet to exploit it on live networks. This issue is patched in version 0.28.0. There are no workarounds.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Tendermint is a high-performance blockchain consensus engine for Byzantine fault tolerant applications. Versions prior to 0.28.0 contain a potential attack via Improper Verification of Cryptographic Signature, affecting anyone using the tendermint-light-client and related packages to perform light client verification (e.g. IBC-rs, Hermes). The light client does not check that the chain IDs of the trusted and untrusted headers match, resulting in a possible attack vector where someone who finds a header from an untrusted chain that satisfies all other verification conditions (e.g. enough overlapping validator signatures) could fool a light client. The attack vector is currently theoretical, and no proof-of-concept exists yet to exploit it on live networks. This issue is patched in version 0.28.0. There are no workarounds.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-23507</guid>
    </item>
    <item>
      <title>GHSA-xqqc-c5gw-c5r5 — Tendermint light client verification not taking into account chain ID</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xqqc-c5gw-c5r5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: tendermint-light-client-verifier, crates.io: tendermint-light-client, crates.io: tendermint-light-client-js&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Anyone using the `tendermint-light-client` and related packages to perform light client verification (e.g. IBC-rs, Hermes).&lt;/p&gt;
&lt;p&gt;At present, the light client does not check that the chain IDs of the trusted and untrusted headers match, resulting in a possible attack vector where someone who finds a header from an untrusted chain that satisfies all other verification conditions (e.g. enough overlapping validator signatures) could fool a light client.&lt;/p&gt;
&lt;p&gt;The attack vector is currently theoretical, and no proof-of-concept exists yet to exploit it on live networks.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Users of the light client-related crates can currently upgrade to `v0.28.0`.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;None&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;- [Light Client specification](https://github.com/tendermint/tendermint/tree/main/spec/light-client)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: tendermint-light-client-verifier, crates.io: tendermint-light-client, crates.io: tendermint-light-client-js&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Anyone using the `tendermint-light-client` and related packages to perform light client verification (e.g. IBC-rs, Hermes).&lt;/p&gt;
&lt;p&gt;At present, the light client does not check that the chain IDs of the trusted and untrusted headers match, resulting in a possible attack vector where someone who finds a header from an untrusted chain that satisfies all other verification conditions (e.g. enough overlapping validator signatures) could fool a light client.&lt;/p&gt;
&lt;p&gt;The attack vector is currently theoretical, and no proof-of-concept exists yet to exploit it on live networks.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Users of the light client-related crates can currently upgrade to `v0.28.0`.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;None&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;- [Light Client specification](https://github.com/tendermint/tendermint/tree/main/spec/light-client)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xqqc-c5gw-c5r5</guid>
    </item>
    <item>
      <title>gsd-2022-23507</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-23507</link>
      <description>gsd-2022-23507</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-23507</guid>
    </item>
  </channel>
</rss>
