<?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://cve.radiocsirt.org</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>Fri, 02 Oct 2026 09:45:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-57175 — social-auth-core has an Improper Authentication issue</title>
      <link>https://cve.radiocsirt.org/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://cve.radiocsirt.org/vuln/cve-2026-57175</guid>
    </item>
    <item>
      <title>GHSA-vq6g-g6c7-5f2j — social-auth-core has an Improper Authentication issue</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vq6g-g6c7-5f2j</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: social-auth-core&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued `AuthnRequest`.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The issue affects applications using the SAML backend together with authenticated account association.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue has been fixed by validating SAML responses against stored `AuthnRequest` IDs.&lt;/p&gt;
&lt;p&gt;Users should upgrade to a patched version.&lt;/p&gt;
&lt;p&gt;Fix:&lt;/p&gt;
&lt;p&gt;* https://github.com/python-social-auth/social-core/pull/1794&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Applications that cannot upgrade immediately should disable SAML account association for already authenticated users.&lt;/p&gt;
&lt;p&gt;If SAML login is not required, the SAML backend can also be disabled by removing it from `SOCIAL_AUTH_AUTHENTICATION_BACKENDS`.&lt;/p&gt;
&lt;p&gt;There is no complete workaround while continuing to allow vulnerable SAML account association.&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;Reported through GitHub private vulnerability reporting by Liyi Zhou, Ziyue Wang, Strick, Maurice, and Chenchen Yu from the University of Sydney security research team.&lt;/p&gt;
&lt;p&gt;Reporter references:&lt;/p&gt;
&lt;p&gt;* https://lzhou1110.github.io/
* https://zyy0530.github.io/
* https://str1ckl4nd.github.io/
* https://maurice.busystar.org/
* https://7thparkk.github.io/&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: social-auth-core&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued `AuthnRequest`.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The issue affects applications using the SAML backend together with authenticated account association.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue has been fixed by validating SAML responses against stored `AuthnRequest` IDs.&lt;/p&gt;
&lt;p&gt;Users should upgrade to a patched version.&lt;/p&gt;
&lt;p&gt;Fix:&lt;/p&gt;
&lt;p&gt;* https://github.com/python-social-auth/social-core/pull/1794&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Applications that cannot upgrade immediately should disable SAML account association for already authenticated users.&lt;/p&gt;
&lt;p&gt;If SAML login is not required, the SAML backend can also be disabled by removing it from `SOCIAL_AUTH_AUTHENTICATION_BACKENDS`.&lt;/p&gt;
&lt;p&gt;There is no complete workaround while continuing to allow vulnerable SAML account association.&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;Reported through GitHub private vulnerability reporting by Liyi Zhou, Ziyue Wang, Strick, Maurice, and Chenchen Yu from the University of Sydney security research team.&lt;/p&gt;
&lt;p&gt;Reporter references:&lt;/p&gt;
&lt;p&gt;* https://lzhou1110.github.io/
* https://zyy0530.github.io/
* https://str1ckl4nd.github.io/
* https://maurice.busystar.org/
* https://7thparkk.github.io/&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vq6g-g6c7-5f2j</guid>
    </item>
  </channel>
</rss>
