<?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-03T05:41:42.346471+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-143653</id>
    <title>EUVD-2026-143653</title>
    <updated>2026-10-03T05:41:42.349096+00:00</updated>
    <content>EUVD-2026-143653</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-143653"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2006-5484</id>
    <title>fkie_cve-2006-5484</title>
    <updated>2026-10-03T05:41:42.349127+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>SSH Tectia Client/Server/Connector 5.1.0 and earlier, Manager 2.2.0 and earlier, and other products, when using an RSA key with exponent 3, removes PKCS-1 padding before generating a hash, which allows remote attackers to forge a PKCS #1 v1.5 signature that is signed by that RSA key and prevents Tectia from correctly verifying X.509 and other certificates that use PKCS #1, a similar issue to CVE-2006-4339.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2006-5484"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-f6g8-8p5j-hphv</id>
    <title>GHSA-f6g8-8p5j-hphv</title>
    <updated>2026-10-03T05:41:42.349159+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>SSH Tectia Client/Server/Connector 5.1.0 and earlier, Manager 2.2.0 and earlier, and other products, when using an RSA key with exponent 3, removes PKCS-1 padding before generating a hash, which allows remote attackers to forge a PKCS #1 v1.5 signature that is signed by that RSA key and prevents Tectia from correctly verifying X.509 and other certificates that use PKCS #1, a similar issue to CVE-2006-4339.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-f6g8-8p5j-hphv"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2006-5484</id>
    <title>gsd-2006-5484</title>
    <updated>2026-10-03T05:41:42.349177+00:00</updated>
    <content>gsd-2006-5484</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2006-5484"/>
  </entry>
</feed>
