<?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 osv_psf</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>Thu, 19 Nov 2026 20:49:30 +0000</lastBuildDate>
    <item>
      <title>PSF-2026-48</title>
      <link>https://vulnerability.circl.lu/vuln/psf-2026-48</link>
      <description>&lt;p&gt;socket.getaddrinfo() previously accepted null bytes within *host* and *port* parameters which can cause the values to be silently truncated.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;socket.getaddrinfo() previously accepted null bytes within *host* and *port* parameters which can cause the values to be silently truncated.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/psf-2026-48</guid>
      <pubDate>Thu, 29 Oct 2026 17:45:47 +0000</pubDate>
    </item>
    <item>
      <title>PSF-2026-47</title>
      <link>https://vulnerability.circl.lu/vuln/psf-2026-47</link>
      <description>&lt;p&gt;Response body and chunk parsing would handle non-hex or negative integers incorrectly which could result in misinterpreting HTTP response contents.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Response body and chunk parsing would handle non-hex or negative integers incorrectly which could result in misinterpreting HTTP response contents.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/psf-2026-47</guid>
      <pubDate>Tue, 27 Oct 2026 19:58:52 +0000</pubDate>
    </item>
    <item>
      <title>PSF-2025-2</title>
      <link>https://vulnerability.circl.lu/vuln/psf-2025-2</link>
      <description>&lt;p&gt;There is a defect in the CPython standard library module “mimetypes” where on Windows the default list of known file locations are writable meaning other users can create invalid files to cause MemoryError to be raised on Python runtime startup or have file extensions be interpreted as the incorrect file type.&lt;/p&gt;
&lt;p&gt;This defect is caused by the default locations of Linux and macOS platforms (such as “/etc/mime.types”) also being used on Windows, where they are user-writable locations (“C:\etc\mime.types”).&lt;/p&gt;
&lt;p&gt;To work-around this issue a user can call mimetypes.init() with an empty list (“[]”) on Windows platforms to avoid using the default list of known file locations.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;There is a defect in the CPython standard library module “mimetypes” where on Windows the default list of known file locations are writable meaning other users can create invalid files to cause MemoryError to be raised on Python runtime startup or have file extensions be interpreted as the incorrect file type.&lt;/p&gt;
&lt;p&gt;This defect is caused by the default locations of Linux and macOS platforms (such as “/etc/mime.types”) also being used on Windows, where they are user-writable locations (“C:\etc\mime.types”).&lt;/p&gt;
&lt;p&gt;To work-around this issue a user can call mimetypes.init() with an empty list (“[]”) on Windows platforms to avoid using the default list of known file locations.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/psf-2025-2</guid>
      <pubDate>Fri, 14 Feb 2025 16:18:00 +0000</pubDate>
    </item>
    <item>
      <title>PSF-2026-45</title>
      <link>https://vulnerability.circl.lu/vuln/psf-2026-45</link>
      <description>&lt;p&gt;tarfile.tar_filter could be bypassed using crafted link entries, including symlinks with empty or directory-like names, to redirect later archive members outside the intended extraction directory. This allowed a malicious tar archive to cause tarfile.extractall() with filter=&amp;#34;tar&amp;#34; to write files outside the destination directory, subject to the permissions of the extracting process.&lt;/p&gt;
&lt;p&gt;This is the tarfile.tar_filter counterpart of CVE-2026-7774, which covered tarfile.data_filter.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;tarfile.tar_filter could be bypassed using crafted link entries, including symlinks with empty or directory-like names, to redirect later archive members outside the intended extraction directory. This allowed a malicious tar archive to cause tarfile.extractall() with filter=&amp;#34;tar&amp;#34; to write files outside the destination directory, subject to the permissions of the extracting process.&lt;/p&gt;
&lt;p&gt;This is the tarfile.tar_filter counterpart of CVE-2026-7774, which covered tarfile.data_filter.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/psf-2026-45</guid>
      <pubDate>Thu, 22 Oct 2026 20:57:36 +0000</pubDate>
    </item>
    <item>
      <title>PSF-2026-42</title>
      <link>https://vulnerability.circl.lu/vuln/psf-2026-42</link>
      <description>&lt;p&gt;The cleanup of tempfile.TemporaryDirectory is vulnerable to a race condition. An attacker who can modify the tree during cleanup can replace a directory with a symbolic link, causing files outside of the temporary directory to be deleted or have their permissions and file flags reset, with the privileges of the process performing the cleanup. Note that platforms where shutil.rmtree.avoids_symlink_attacks is false, remain affected, and file flags may still be reset outside of the tree on all platforms.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The cleanup of tempfile.TemporaryDirectory is vulnerable to a race condition. An attacker who can modify the tree during cleanup can replace a directory with a symbolic link, causing files outside of the temporary directory to be deleted or have their permissions and file flags reset, with the privileges of the process performing the cleanup. Note that platforms where shutil.rmtree.avoids_symlink_attacks is false, remain affected, and file flags may still be reset outside of the tree on all platforms.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/psf-2026-42</guid>
      <pubDate>Tue, 29 Sep 2026 17:46:01 +0000</pubDate>
    </item>
    <item>
      <title>PSF-2026-46</title>
      <link>https://vulnerability.circl.lu/vuln/psf-2026-46</link>
      <description>&lt;p&gt;Python has added a denylist for known compromised certificates to the &amp;#34;ssl&amp;#34; module to ensure user safety even without certificate revocation configured. Known compromised certificates will automatically be rejected regardless of the SSLContext policy configuration.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Python has added a denylist for known compromised certificates to the &amp;#34;ssl&amp;#34; module to ensure user safety even without certificate revocation configured. Known compromised certificates will automatically be rejected regardless of the SSLContext policy configuration.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/psf-2026-46</guid>
      <pubDate>Sat, 24 Oct 2026 14:15:14 +0000</pubDate>
    </item>
    <item>
      <title>PSF-2026-41</title>
      <link>https://vulnerability.circl.lu/vuln/psf-2026-41</link>
      <description>&lt;p&gt;In CPython 3.13 and earlier, the tarfile module&amp;#39;s data and tar extraction filters are vulnerable to crafted archives containing a hard link to a symbolic link. Such archives may cause extraction to modify the permissions or modification time of a file outside the destination directory, or expose the contents of that file within the extracted tree.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In CPython 3.13 and earlier, the tarfile module&amp;#39;s data and tar extraction filters are vulnerable to crafted archives containing a hard link to a symbolic link. Such archives may cause extraction to modify the permissions or modification time of a file outside the destination directory, or expose the contents of that file within the extracted tree.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/psf-2026-41</guid>
      <pubDate>Mon, 14 Sep 2026 19:14:03 +0000</pubDate>
    </item>
    <item>
      <title>PSF-2026-40</title>
      <link>https://vulnerability.circl.lu/vuln/psf-2026-40</link>
      <description>&lt;p&gt;When tarfile extracts a link on a system that doesn&amp;#39;t support links, it falls back to extracting a member from the archive. In this case, the filter function is run twice: once for the extracted member, and once with name set to the location of the link. For one of the calls, the return value was ignored. Instead, the member should be skipped if either call returns None.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;When tarfile extracts a link on a system that doesn&amp;#39;t support links, it falls back to extracting a member from the archive. In this case, the filter function is run twice: once for the extracted member, and once with name set to the location of the link. For one of the calls, the return value was ignored. Instead, the member should be skipped if either call returns None.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/psf-2026-40</guid>
      <pubDate>Fri, 11 Sep 2026 17:27:04 +0000</pubDate>
    </item>
    <item>
      <title>PSF-2026-39</title>
      <link>https://vulnerability.circl.lu/vuln/psf-2026-39</link>
      <description>&lt;p&gt;When decompressing crafted zip files using the bzip/LZMA/Zstandard&lt;/p&gt;
&lt;p&gt;compressions, Python could use an attacker-controlled size to&lt;/p&gt;
&lt;p&gt;pre-allocate memory, possibly resulting in memory exhaustion.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;When decompressing crafted zip files using the bzip/LZMA/Zstandard&lt;/p&gt;
&lt;p&gt;compressions, Python could use an attacker-controlled size to&lt;/p&gt;
&lt;p&gt;pre-allocate memory, possibly resulting in memory exhaustion.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/psf-2026-39</guid>
      <pubDate>Tue, 25 Aug 2026 15:07:58 +0000</pubDate>
    </item>
    <item>
      <title>PSF-2026-36</title>
      <link>https://vulnerability.circl.lu/vuln/psf-2026-36</link>
      <description>&lt;p&gt;The HTTPPasswordMgr class in the urllib.request module, along with its subclasses HTTPPasswordMgrWithDefaultRealm and HTTPPasswordMgrWithPriorAuth, did not take the URL scheme into account when matching stored credentials against a requested URL. Credentials added for an https:// URL were also used for requests to the same host over http://, so an attacker able to redirect or downgrade a client to plain HTTP (for example, via an HTTPS-to-HTTP redirect or an on-path position) could capture credentials in cleartext. Credentials added for http:// URLs could likewise be sent over https://.&lt;/p&gt;
&lt;p&gt;Credential matching is now scoped by URL scheme. Credentials registered with a URL that includes a scheme are only used for requests with the same scheme. Credentials registered with a bare authority (such as example.com or example.com:8080) continue to match any scheme, preserving compatibility with existing code, including proxy authentication.&lt;/p&gt;
&lt;p&gt;Users who cannot upgrade immediately can mitigate by ensuring that applications never make plain http:// requests to hosts for which credentials are registered, for example by not following redirects to http:// URLs.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The HTTPPasswordMgr class in the urllib.request module, along with its subclasses HTTPPasswordMgrWithDefaultRealm and HTTPPasswordMgrWithPriorAuth, did not take the URL scheme into account when matching stored credentials against a requested URL. Credentials added for an https:// URL were also used for requests to the same host over http://, so an attacker able to redirect or downgrade a client to plain HTTP (for example, via an HTTPS-to-HTTP redirect or an on-path position) could capture credentials in cleartext. Credentials added for http:// URLs could likewise be sent over https://.&lt;/p&gt;
&lt;p&gt;Credential matching is now scoped by URL scheme. Credentials registered with a URL that includes a scheme are only used for requests with the same scheme. Credentials registered with a bare authority (such as example.com or example.com:8080) continue to match any scheme, preserving compatibility with existing code, including proxy authentication.&lt;/p&gt;
&lt;p&gt;Users who cannot upgrade immediately can mitigate by ensuring that applications never make plain http:// requests to hosts for which credentials are registered, for example by not following redirects to http:// URLs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/psf-2026-36</guid>
      <pubDate>Tue, 18 Aug 2026 15:50:57 +0000</pubDate>
    </item>
  </channel>
</rss>
