<?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>Sun, 22 Nov 2026 15:56:30 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-133949</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-133949</link>
      <description>&lt;p&gt;pip prior to v26.2.2 the certifi bundled with pip contains the compromised eMudhra certificates.&lt;/p&gt;
&lt;p&gt;Upgrading to a secure version of pip should be done either by first upgrading Python to a version that rejects the compromised intermediates (CVE-2026-115557) or use hash pinning with a known-secure version of pip. pip is not vulnerable when using a Python version that rejects the compromised certificates. See the references below for more information.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;pip prior to v26.2.2 the certifi bundled with pip contains the compromised eMudhra certificates.&lt;/p&gt;
&lt;p&gt;Upgrading to a secure version of pip should be done either by first upgrading Python to a version that rejects the compromised intermediates (CVE-2026-115557) or use hash pinning with a known-secure version of pip. pip is not vulnerable when using a Python version that rejects the compromised certificates. See the references below for more information.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-133949</guid>
    </item>
    <item>
      <title>GHSA-jg88-vh4g-v698</title>
      <link>https://db.gcve.eu/vuln/ghsa-jg88-vh4g-v698</link>
      <description>&lt;p&gt;pip prior to v26.2.2 the certifi bundled with pip contains the compromised eMudhra certificates.&lt;/p&gt;
&lt;p&gt;Upgrading to a secure version of pip should be done either by first upgrading Python to a version that rejects the compromised intermediates (CVE-2026-115557) or use hash pinning with a known-secure version of pip. pip is not vulnerable when using a Python version that rejects the compromised certificates. See the references below for more information.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;pip prior to v26.2.2 the certifi bundled with pip contains the compromised eMudhra certificates.&lt;/p&gt;
&lt;p&gt;Upgrading to a secure version of pip should be done either by first upgrading Python to a version that rejects the compromised intermediates (CVE-2026-115557) or use hash pinning with a known-secure version of pip. pip is not vulnerable when using a Python version that rejects the compromised certificates. See the references below for more information.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-jg88-vh4g-v698</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-133949 — pip bundles compromised eMudhra certificates via certifi</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-133949</link>
      <description>msrc_CVE-2026-133949</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-133949</guid>
    </item>
  </channel>
</rss>
