<?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-12T20:34:50.447109+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/bit-envoy-2022-21656</id>
    <title>BIT-envoy-2022-21656 — X.509 subjectAltName matching bypass in Envoy</title>
    <updated>2026-10-12T20:34:50.480507+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: envoy</p>
<p>Envoy is an open source edge and service proxy, designed for cloud-native applications. The default_validator.cc implementation used to implement the default certificate validation routines has a "type confusion" bug when processing subjectAltNames. This processing allows, for example, an rfc822Name or uniformResourceIndicator to be authenticated as a domain name. This confusion allows for the bypassing of nameConstraints, as processed by the underlying OpenSSL/BoringSSL implementation, exposing the possibility of impersonation of arbitrary servers. As a result Envoy will trust upstream certificates that should not be trusted.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-envoy-2022-21656"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2022-16290</id>
    <title>cnvd-2022-16290</title>
    <updated>2026-10-12T20:34:50.480557+00:00</updated>
    <content>cnvd-2022-16290</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2022-16290"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-234414</id>
    <title>EUVD-2026-234414</title>
    <updated>2026-10-12T20:34:50.480574+00:00</updated>
    <content>EUVD-2026-234414</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-234414"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2022-21656</id>
    <title>fkie_cve-2022-21656</title>
    <updated>2026-10-12T20:34:50.480586+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Envoy is an open source edge and service proxy, designed for cloud-native applications. The default_validator.cc implementation used to implement the default certificate validation routines has a "type confusion" bug when processing subjectAltNames. This processing allows, for example, an rfc822Name or uniformResourceIndicator to be authenticated as a domain name. This confusion allows for the bypassing of nameConstraints, as processed by the underlying OpenSSL/BoringSSL implementation, exposing the possibility of impersonation of arbitrary servers. As a result Envoy will trust upstream certificates that should not be trusted.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2022-21656"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2022-21656</id>
    <title>gsd-2022-21656</title>
    <updated>2026-10-12T20:34:50.480609+00:00</updated>
    <content>gsd-2022-21656</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2022-21656"/>
  </entry>
</feed>
