<?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://db.gcve.eu</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>Tue, 13 Oct 2026 20:52:49 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-103503</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-103503</link>
      <description>&lt;p&gt;Improper Certificate Validation vulnerability in hexpm hex allows an attacker who can intercept HTTPS connections, and holds a certificate for a Hex host issued by a CA in Hex&amp;#39;s bundled CA store, to impersonate that host to users who set cacerts_path to a CA store that leaves that CA out.&lt;/p&gt;
&lt;p&gt;cacerts_path (HEX_CACERTS_PATH) is documented as the path to the CA certificate store, used instead of the CA bundle that ships with Hex. Hex.HTTP.SSL.ssl_opts/1 passes the configured store as the cacerts option, but builds the partial_chain callback from the bundled store whether cacerts_path is set or not. Hex.HTTP.SSL.partial_chain/2 accepts a server chain when any certificate in it has the same public key as a bundled CA certificate, so a chain that leads to a bundled CA passes verification although the configured store doesn&amp;#39;t contain that CA. Hostname verification still applies.&lt;/p&gt;
&lt;p&gt;This issue affects hex: from 0.20.2 before 2.5.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Improper Certificate Validation vulnerability in hexpm hex allows an attacker who can intercept HTTPS connections, and holds a certificate for a Hex host issued by a CA in Hex&amp;#39;s bundled CA store, to impersonate that host to users who set cacerts_path to a CA store that leaves that CA out.&lt;/p&gt;
&lt;p&gt;cacerts_path (HEX_CACERTS_PATH) is documented as the path to the CA certificate store, used instead of the CA bundle that ships with Hex. Hex.HTTP.SSL.ssl_opts/1 passes the configured store as the cacerts option, but builds the partial_chain callback from the bundled store whether cacerts_path is set or not. Hex.HTTP.SSL.partial_chain/2 accepts a server chain when any certificate in it has the same public key as a bundled CA certificate, so a chain that leads to a bundled CA passes verification although the configured store doesn&amp;#39;t contain that CA. Hostname verification still applies.&lt;/p&gt;
&lt;p&gt;This issue affects hex: from 0.20.2 before 2.5.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-103503</guid>
    </item>
  </channel>
</rss>
