<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T13:25:53.228386+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2024-35195</id>
    <title>CVE-2024-35195 — Requests `Session` object does not verify requests after making first request with verify=False</title>
    <updated>2026-10-02T13:25:53.272601+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> psf requests, request_project request</p>
<p>Requests is a HTTP library. Prior to 2.32.0, when making requests through a Requests `Session`, if the first request is made with `verify=False` to disable cert verification, all subsequent requests to the same host will continue to ignore cert verification regardless of changes to the value of `verify`. This behavior will continue for the lifecycle of the connection in the connection pool. This vulnerability is fixed in 2.32.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2024-35195"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-58qw-9mgm-455v</id>
    <title>GHSA-58qw-9mgm-455v — pip has an interpretation conflict due to handling both concatenated tar and ZIP files as ZIP files</title>
    <updated>2026-10-02T13:25:53.272664+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: pip</p>
<p>pip handles concatenated tar and ZIP files as ZIP files regardless of filename or whether a file is both a tar and ZIP file. This behavior could result in confusing installation behavior, such as installing "incorrect" files according to the filename of the archive. New behavior only proceeds with installation if the file identifies uniquely as a ZIP or tar archive, not as both.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-58qw-9mgm-455v"/>
  </entry>
</feed>
