<?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>Fri, 09 Oct 2026 18:44:58 +0000</lastBuildDate>
    <item>
      <title>cnvd-2018-01934</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2018-01934</link>
      <description>cnvd-2018-01934</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2018-01934</guid>
    </item>
    <item>
      <title>EUVD-2026-205420</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-205420</link>
      <description>EUVD-2026-205420</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-205420</guid>
    </item>
    <item>
      <title>fkie_cve-2018-0114</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2018-0114</link>
      <description>&lt;p&gt;A vulnerability in the Cisco node-jose open source library before 0.11.0 could allow an unauthenticated, remote attacker to re-sign tokens using a key that is embedded within the token. The vulnerability is due to node-jose following the JSON Web Signature (JWS) standard for JSON Web Tokens (JWTs). This standard specifies that a JSON Web Key (JWK) representing a public key can be embedded within the header of a JWS. This public key is then trusted for verification. An attacker could exploit this by forging valid JWS objects by removing the original signature, adding a new public key to the header, and then signing the object using the (attacker-owned) private key associated with the public key embedded in that JWS header.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A vulnerability in the Cisco node-jose open source library before 0.11.0 could allow an unauthenticated, remote attacker to re-sign tokens using a key that is embedded within the token. The vulnerability is due to node-jose following the JSON Web Signature (JWS) standard for JSON Web Tokens (JWTs). This standard specifies that a JSON Web Key (JWK) representing a public key can be embedded within the header of a JWS. This public key is then trusted for verification. An attacker could exploit this by forging valid JWS objects by removing the original signature, adding a new public key to the header, and then signing the object using the (attacker-owned) private key associated with the public key embedded in that JWS header.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2018-0114</guid>
    </item>
    <item>
      <title>GHSA-jfxm-w8g2-4rcv — Cisco node-jose improper validation of JWT signature</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jfxm-w8g2-4rcv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: node-jose&lt;/p&gt;
&lt;p&gt;A vulnerability in the Cisco node-jose open source library before 0.11.0 could allow an unauthenticated, remote attacker to re-sign tokens using a key that is embedded within the token. The vulnerability is due to node-jose following the JSON Web Signature (JWS) standard for JSON Web Tokens (JWTs). This standard specifies that a JSON Web Key (JWK) representing a public key can be embedded within the header of a JWS. This public key is then trusted for verification. An attacker could exploit this by forging valid JWS objects by removing the original signature, adding a new public key to the header, and then signing the object using the (attacker-owned) private key associated with the public key embedded in that JWS header.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: node-jose&lt;/p&gt;
&lt;p&gt;A vulnerability in the Cisco node-jose open source library before 0.11.0 could allow an unauthenticated, remote attacker to re-sign tokens using a key that is embedded within the token. The vulnerability is due to node-jose following the JSON Web Signature (JWS) standard for JSON Web Tokens (JWTs). This standard specifies that a JSON Web Key (JWK) representing a public key can be embedded within the header of a JWS. This public key is then trusted for verification. An attacker could exploit this by forging valid JWS objects by removing the original signature, adding a new public key to the header, and then signing the object using the (attacker-owned) private key associated with the public key embedded in that JWS header.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jfxm-w8g2-4rcv</guid>
    </item>
    <item>
      <title>gsd-2018-0114</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2018-0114</link>
      <description>gsd-2018-0114</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2018-0114</guid>
    </item>
  </channel>
</rss>
