<?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 all</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>Tue, 29 Sep 2026 10:37:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-57175 — social-auth-core has an Improper Authentication issue</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-57175</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; python-social-auth social-core&lt;/p&gt;
&lt;p&gt;Python Social Auth is a social authentication/registration mechanism. Prior to version 5.0.0, the SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued `AuthnRequest`. Applications using SAML account association could allow an attacker with a valid account on a trusted IdP to link the attacker&amp;#39;s SAML identity to a logged-in victim&amp;#39;s local account. The attacker could then authenticate through SAML and gain access to the victim&amp;#39;s account. The issue affects applications using the SAML backend together with authenticated account association. The issue has been fixed in version 5.0.0 by validating SAML responses against stored `AuthnRequest` IDs.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; python-social-auth social-core&lt;/p&gt;
&lt;p&gt;Python Social Auth is a social authentication/registration mechanism. Prior to version 5.0.0, the SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued `AuthnRequest`. Applications using SAML account association could allow an attacker with a valid account on a trusted IdP to link the attacker&amp;#39;s SAML identity to a logged-in victim&amp;#39;s local account. The attacker could then authenticate through SAML and gain access to the victim&amp;#39;s account. The issue affects applications using the SAML backend together with authenticated account association. The issue has been fixed in version 5.0.0 by validating SAML responses against stored `AuthnRequest` IDs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-57175</guid>
    </item>
  </channel>
</rss>
