<?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>Wed, 14 Oct 2026 15:03:05 +0000</lastBuildDate>
    <item>
      <title>cnvd-2017-04896</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2017-04896</link>
      <description>cnvd-2017-04896</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2017-04896</guid>
    </item>
    <item>
      <title>EUVD-2026-87631</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-87631</link>
      <description>EUVD-2026-87631</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-87631</guid>
    </item>
    <item>
      <title>fkie_cve-2016-9122</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2016-9122</link>
      <description>&lt;p&gt;go-jose before 1.0.4 suffers from multiple signatures exploitation. The go-jose library supports messages with multiple signatures. However, when validating a signed message the API did not indicate which signature was valid, which could potentially lead to confusion. For example, users of the library might mistakenly read protected header values from an attached signature that was different from the one originally validated.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;go-jose before 1.0.4 suffers from multiple signatures exploitation. The go-jose library supports messages with multiple signatures. However, when validating a signed message the API did not indicate which signature was valid, which could potentially lead to confusion. For example, users of the library might mistakenly read protected header values from an attached signature that was different from the one originally validated.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2016-9122</guid>
    </item>
    <item>
      <title>GHSA-77gc-fj98-665h — Go JOSE Signature Validation Bypass</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-77gc-fj98-665h</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: gopkg.in/square/go-jose.v1&lt;/p&gt;
&lt;p&gt;Go JOSE before 1.1.0 suffers from multiple signatures exploitation. The go-jose library supports messages with multiple signatures. However, when validating a signed message the API did not indicate which signature was valid, which could potentially lead to confusion. For example, users of the library might mistakenly read protected header values from an attached signature that was different from the one originally validated&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: gopkg.in/square/go-jose.v1&lt;/p&gt;
&lt;p&gt;Go JOSE before 1.1.0 suffers from multiple signatures exploitation. The go-jose library supports messages with multiple signatures. However, when validating a signed message the API did not indicate which signature was valid, which could potentially lead to confusion. For example, users of the library might mistakenly read protected header values from an attached signature that was different from the one originally validated&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-77gc-fj98-665h</guid>
    </item>
    <item>
      <title>gsd-2016-9122</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2016-9122</link>
      <description>gsd-2016-9122</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2016-9122</guid>
    </item>
  </channel>
</rss>
