<?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-03T01:40:46.520911+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-2025-61783</id>
    <title>CVE-2025-61783 — Python Social Auth - Django has unsafe account association</title>
    <updated>2026-10-03T01:40:46.557931+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> python-social-auth social-app-django</p>
<p>Python Social Auth is a social authentication/registration mechanism. In versions prior to 5.6.0, upon authentication, the user could be associated by e-mail even if the `associate_by_email` pipeline was not included. This could lead to account compromise when a third-party authentication service does not validate provided e-mail addresses or doesn't require unique e-mail addresses. Version 5.6.0 contains a patch. As a workaround, review the authentication service policy on e-mail addresses; many will not allow exploiting this vulnerability.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2025-61783"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-wv4w-6qv2-qqfg</id>
    <title>GHSA-wv4w-6qv2-qqfg — Python Social Auth - Django has unsafe account association</title>
    <updated>2026-10-03T01:40:46.558016+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: social-auth-app-django</p>
<p>### Impact</p>
<p>Upon authentication, the user could be associated by e-mail even if the `associate_by_email` pipeline was not included. This could lead to account compromise when a third-party authentication service does not validate provided e-mail addresses or doesn't require unique e-mail addresses.</p>
<p>### Patches</p>
<p>* https://github.com/python-social-auth/social-app-django/pull/803</p>
<p>### Workarounds</p>
<p>Review the authentication service policy on e-mail addresses; many will not allow exploiting this vulnerability.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-wv4w-6qv2-qqfg"/>
  </entry>
</feed>
