<?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-12T17:35:42.883888+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-318768</id>
    <title>EUVD-2026-318768</title>
    <updated>2026-10-12T17:35:42.926609+00:00</updated>
    <content>EUVD-2026-318768</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-318768"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-44088</id>
    <title>fkie_cve-2026-44088</title>
    <updated>2026-10-12T17:35:42.926643+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>SzafirHost verifies the signature of the downloaded JAR file using class JarInputStream (reading from the beginning of the file), but loads classes using class JarFile/URLClassLoader (reading the Central Directory from the end). It can lead to remote code execution by allowing an attacker to combine a genuine, signed JAR file with a malicious ZIP file, causing the verification to pass but the malicious class to be loaded.</p>
<p>This issue was fixed in version 1.2.1.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-44088"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-j8f8-frc5-vgc6</id>
    <title>GHSA-j8f8-frc5-vgc6</title>
    <updated>2026-10-12T17:35:42.926678+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>SzafirHost verifies the signature of the downloaded JAR file using class JarInputStream (reading from the beginning of the file), but loads classes using class JarFile/URLClassLoader (reading the Central Directory from the end). It can lead to remote code execution by allowing an attacker to combine a genuine, signed JAR file with a malicious ZIP file, causing the verification to pass but the malicious class to be loaded.</p>
<p>This issue was fixed in version 1.2.1.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-j8f8-frc5-vgc6"/>
  </entry>
</feed>
