<?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-11-16T20:02:16.376713+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-391503</id>
    <title>EUVD-2026-391503</title>
    <updated>2026-11-16T20:02:16.379971+00:00</updated>
    <content>EUVD-2026-391503</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-391503"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-111815</id>
    <title>fkie_cve-2026-111815</title>
    <updated>2026-11-16T20:02:16.380001+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>Apache Traffic Server can resume a TLS session across SNI virtual hosts without re-verifying a client certificate required by the resumed host's verify_client STRICT policy.</p>
<p>This issue affects Apache Traffic Server: from 8.0.0 through 8.1.11, from 9.0.0 through 9.2.15, from 10.0.0 through 10.1.4, 10.2.0.</p>
<p>Users are recommended to upgrade to version 9.2.16, 10.1.5, or 10.2.1, which fix the issue.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-111815"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-h35r-68fc-8f5m</id>
    <title>GHSA-h35r-68fc-8f5m</title>
    <updated>2026-11-16T20:02:16.380034+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>Apache Traffic Server can resume a TLS session across SNI virtual hosts without re-verifying a client certificate required by the resumed host's verify_client STRICT policy.</p>
<p>This issue affects Apache Traffic Server: from 8.0.0 through 8.1.11, from 9.0.0 through 9.2.15, from 10.0.0 through 10.1.4, 10.2.0.</p>
<p>Users are recommended to upgrade to version 9.2.16, 10.1.5, or 10.2.1, which fix the issue.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-h35r-68fc-8f5m"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-111815</id>
    <title>UBUNTU-CVE-2026-111815</title>
    <updated>2026-11-16T20:02:16.380053+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:16.04:LTS: trafficserver, Ubuntu:18.04:LTS: trafficserver, Ubuntu:Pro:20.04:LTS: trafficserver, Ubuntu:Pro:22.04:LTS: trafficserver, Ubuntu:24.04:LTS: trafficserver</p>
<p>Apache Traffic Server can resume a TLS session across SNI virtual hosts without re-verifying a client certificate required by the resumed host's verify_client STRICT policy. This issue affects Apache Traffic Server: from 8.0.0 through 8.1.11, from 9.0.0 through 9.2.15, from 10.0.0 through 10.1.4, 10.2.0. Users are recommended to upgrade to version 9.2.16, 10.1.5, or 10.2.1, which fix the issue.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-111815"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4112</id>
    <title>WID-SEC-W-2026-4112 — Apache Traffic Server: Mehrere Schwachstellen</title>
    <updated>2026-11-16T20:02:16.380082+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Apache Traffic Server ausnutzen, um beliebigen Programmcode auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand auszulösen sowie Daten zu manipulieren oder offenzulegen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4112"/>
  </entry>
</feed>
