<?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:34:22.841909+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/bdu:2020-05737</id>
    <title>bdu:2020-05737</title>
    <updated>2026-10-03T05:34:22.954186+00:00</updated>
    <content>bdu:2020-05737</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2020-05737"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bit-envoy-2020-8660</id>
    <title>BIT-envoy-2020-8660</title>
    <updated>2026-10-03T05:34:22.954225+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: envoy</p>
<p>CNCF Envoy through 1.13.0 TLS inspector bypass. TLS inspector could have been bypassed (not recognized as a TLS client) by a client using only TLS 1.3. Because TLS extensions (SNI, ALPN) were not inspected, those connections might have been matched to a wrong filter chain, possibly bypassing some security restrictions in the process.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-envoy-2020-8660"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2020-20727</id>
    <title>cnvd-2020-20727</title>
    <updated>2026-10-03T05:34:22.954259+00:00</updated>
    <content>cnvd-2020-20727</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2020-20727"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-38561</id>
    <title>EUVD-2026-38561</title>
    <updated>2026-10-03T05:34:22.954274+00:00</updated>
    <content>EUVD-2026-38561</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-38561"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2020-8660</id>
    <title>fkie_cve-2020-8660</title>
    <updated>2026-10-03T05:34:22.954286+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>CNCF Envoy through 1.13.0 TLS inspector bypass. TLS inspector could have been bypassed (not recognized as a TLS client) by a client using only TLS 1.3. Because TLS extensions (SNI, ALPN) were not inspected, those connections might have been matched to a wrong filter chain, possibly bypassing some security restrictions in the process.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2020-8660"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2020-8660</id>
    <title>gsd-2020-8660</title>
    <updated>2026-10-03T05:34:22.954308+00:00</updated>
    <content>gsd-2020-8660</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2020-8660"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2020:0734</id>
    <title>RHSA-2020:0734 — Red Hat Security Advisory: Red Hat OpenShift Service Mesh 1.0.9 servicemesh-proxy security update</title>
    <updated>2026-10-03T05:34:22.954318+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>envoy: Excessive CPU and/or memory usage when proxying HTTP/1.1 envoy: TLS inspector bypassc envoy: Response flooding for HTTP/1.1 envoy: Incorrect Access Control when using SDS with Combined Validation Context</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2020:0734"/>
  </entry>
</feed>
