<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>RADAR — Python security announcements</title>
    <link>https://radar.trulysovereign.com</link>
    <atom:link href="https://radar.trulysovereign.com/feeds/source/python-security-announcements.xml" rel="self" type="application/rss+xml"/>
    <description>Changes RADAR detected at Python security announcements.</description>
    <language>en</language>
    <lastBuildDate>Sat, 21 Nov 2026 19:19:18 GMT</lastBuildDate>
    <item>
      <title>pip prior to v26.2.2 bundles compromised eMudhra certificates</title>
      <link>https://radar.trulysovereign.com/items/9dd24bbc-1f5b-4a07-885f-9467aaa0fd0d</link>
      <guid isPermaLink="false">9dd24bbc-1f5b-4a07-885f-9467aaa0fd0d</guid>
      <pubDate>Sat, 21 Nov 2026 07:10:51 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://mail.python.org/archives/list/security-announce@python.org/message/4234WU4ONSVWPT3BIGG6TOJO2UFE26Y6/">Python security announcements</source>
      <description>pip versions before v26.2.2 include certifi with compromised eMudhra certificates. The vulnerability is rated CRITICAL severity and tracked as CVE-2026-133949.

Why it matters: Compromised certificate authorities can issue fraudulent certificates for any domain, enabling man-in-the-middle attacks on HTTPS connections made by pip during package installation. Any system using affected pip versions is vulnerable when downloading packages.

What to do: Upgrade pip to v26.2.2 or later. If upgrading pip directly, first upgrade Python to a version that rejects the compromised intermediates (CVE-2026-115557), or use hash pinning with a known-secure pip version during the upgrade process.</description>
    </item>
  </channel>
</rss>
