<?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-17T11:22:24.765144+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/euvd-2026-116716</id>
    <title>EUVD-2026-116716</title>
    <updated>2026-10-17T11:22:24.771076+00:00</updated>
    <content>EUVD-2026-116716</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-116716"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2011-4138</id>
    <title>fkie_cve-2011-4138</title>
    <updated>2026-10-17T11:22:24.771123+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 originally tests a URL's validity through a HEAD request, but then uses a GET request for the new target URL in the case of a redirect, which might allow remote attackers to trigger arbitrary GET requests with an unintended source IP address via a crafted Location header.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2011-4138"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-wxg3-mfph-qg9w</id>
    <title>GHSA-wxg3-mfph-qg9w — Django Might Allow CSRF Requests via URL Verification</title>
    <updated>2026-10-17T11:22:24.771179+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: Django</p>
<p>The `verify_exists` functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 originally tests a URL's validity through a HEAD request, but then uses a GET request for the new target URL in the case of a redirect, which might allow remote attackers to trigger arbitrary GET requests with an unintended source IP address via a crafted Location header.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-wxg3-mfph-qg9w"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2011-4138</id>
    <title>gsd-2011-4138</title>
    <updated>2026-10-17T11:22:24.771226+00:00</updated>
    <content>gsd-2011-4138</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2011-4138"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2011-3</id>
    <title>PYSEC-2011-3</title>
    <updated>2026-10-17T11:22:24.771250+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: django</p>
<p>The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 originally tests a URL's validity through a HEAD request, but then uses a GET request for the new target URL in the case of a redirect, which might allow remote attackers to trigger arbitrary GET requests with an unintended source IP address via a crafted Location header.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2011-3"/>
  </entry>
</feed>
