<?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-05T12:19:05.763658+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-45992</id>
    <title>EUVD-2026-45992</title>
    <updated>2026-10-05T12:19:05.826891+00:00</updated>
    <content>EUVD-2026-45992</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-45992"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2020-26234</id>
    <title>fkie_cve-2020-26234</title>
    <updated>2026-10-05T12:19:05.826930+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Opencast before versions 8.9 and 7.9 disables HTTPS hostname verification of its HTTP client used for a large portion of Opencast's HTTP requests. Hostname verification is an important part when using HTTPS to ensure that the presented certificate is valid for the host. Disabling it can allow for man-in-the-middle attacks. This problem is fixed in Opencast 7.9 and Opencast 8.8 Please be aware that fixing the problem means that Opencast will not simply accept any self-signed certificates any longer without properly importing them. If you need those, please make sure to import them into the Java key store. Better yet, get a valid certificate.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2020-26234"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-44cw-p2hm-gpf6</id>
    <title>GHSA-44cw-p2hm-gpf6 — Disabled Hostname Verification in Opencast</title>
    <updated>2026-10-05T12:19:05.826968+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: org.opencastproject:opencast-kernel</p>
<p>Opencast before version 8.9 and 7.9 disables HTTPS hostname verification of its HTTP client used for a large portion of Opencast's HTTP requests.</p>
<p>Hostname verification is an important part when using HTTPS to ensure that the presented certificate is valid for the host. Disabling it can allow for man-in-the-middle attacks.</p>
<p>### Patches</p>
<p>This problem is fixed in Opencast 7.9 and Opencast 8.9</p>
<p>### Self-Signed Certificates</p>
<p>Please be aware that fixing the problem means that Opencast will not simply accept any self-signed certificates any longer without properly importing them. If you need those, please make sure to import them into the Java key store. Better yet, get a valid certificate e.g. from [Let's Encrypt](https://letsencrypt.org).</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-44cw-p2hm-gpf6"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2020-26234</id>
    <title>gsd-2020-26234</title>
    <updated>2026-10-05T12:19:05.827004+00:00</updated>
    <content>gsd-2020-26234</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2020-26234"/>
  </entry>
</feed>
