<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 11:10:36 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2023-52892</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2023-52892</link>
      <description>&lt;p&gt;In phpseclib before 1.0.22, 2.x before 2.0.46, and 3.x before 3.0.33, some characters in Subject Alternative Name fields in TLS certificates are incorrectly allowed to have a special meaning in regular expressions (such as a + wildcard), leading to name confusion in X.509 certificate host verification.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In phpseclib before 1.0.22, 2.x before 2.0.46, and 3.x before 3.0.33, some characters in Subject Alternative Name fields in TLS certificates are incorrectly allowed to have a special meaning in regular expressions (such as a + wildcard), leading to name confusion in X.509 certificate host verification.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2023-52892</guid>
    </item>
    <item>
      <title>GHSA-ff7q-6vwh-v9m4 — Name confusion in x509 Subject Alternative Name fields</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-ff7q-6vwh-v9m4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: phpseclib/phpseclib&lt;/p&gt;
&lt;p&gt;In phpseclib before 1.0.22, 2.x before 2.0.46, and 3.x before 3.0.33, some characters in Subject Alternative Name fields in TLS certificates are incorrectly allowed to have a special meaning in regular expressions (such as a + wildcard), leading to name confusion in X.509 certificate host verification.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: phpseclib/phpseclib&lt;/p&gt;
&lt;p&gt;In phpseclib before 1.0.22, 2.x before 2.0.46, and 3.x before 3.0.33, some characters in Subject Alternative Name fields in TLS certificates are incorrectly allowed to have a special meaning in regular expressions (such as a + wildcard), leading to name confusion in X.509 certificate host verification.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-ff7q-6vwh-v9m4</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-52892</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-52892</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: php-phpseclib, Ubuntu:Pro:16.04:LTS: phpseclib, Ubuntu:Pro:18.04:LTS: php-phpseclib, Ubuntu:Pro:18.04:LTS: phpseclib, Ubuntu:Pro:20.04:LTS: php-phpseclib, Ubuntu:Pro:20.04:LTS: phpseclib, Ubuntu:Pro:22.04:LTS: php-phpseclib, Ubuntu:Pro:22.04:LTS: php-phpseclib3, Ubuntu:Pro:22.04:LTS: phpseclib&lt;/p&gt;
&lt;p&gt;In phpseclib before 1.0.22, 2.x before 2.0.46, and 3.x before 3.0.33, some characters in Subject Alternative Name fields in TLS certificates are incorrectly allowed to have a special meaning in regular expressions (such as a + wildcard), leading to name confusion in X.509 certificate host verification.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: php-phpseclib, Ubuntu:Pro:16.04:LTS: phpseclib, Ubuntu:Pro:18.04:LTS: php-phpseclib, Ubuntu:Pro:18.04:LTS: phpseclib, Ubuntu:Pro:20.04:LTS: php-phpseclib, Ubuntu:Pro:20.04:LTS: phpseclib, Ubuntu:Pro:22.04:LTS: php-phpseclib, Ubuntu:Pro:22.04:LTS: php-phpseclib3, Ubuntu:Pro:22.04:LTS: phpseclib&lt;/p&gt;
&lt;p&gt;In phpseclib before 1.0.22, 2.x before 2.0.46, and 3.x before 3.0.33, some characters in Subject Alternative Name fields in TLS certificates are incorrectly allowed to have a special meaning in regular expressions (such as a + wildcard), leading to name confusion in X.509 certificate host verification.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-52892</guid>
    </item>
  </channel>
</rss>
