<?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 11:08:36 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-375388</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-375388</link>
      <description>EUVD-2026-375388</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-375388</guid>
    </item>
    <item>
      <title>fkie_cve-2026-57179</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-57179</link>
      <description>&lt;p&gt;Python Social Auth is a social authentication/registration mechanism. Prior to version 5.0.0, the partial-pipeline resume mechanism accepted `partial_token` as a bearer credential without binding it to the browser session that created it. Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim&amp;#39;s browser to resume that attacker-controlled flow. This could authenticate the victim&amp;#39;s browser as the attacker&amp;#39;s account. The issue affects applications using partial pipeline steps such as `mail_validation` or custom steps decorated with `@partial`. The issue has been fixed in version 5.0.0 by binding partial pipeline resumes to the originating browser session.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Python Social Auth is a social authentication/registration mechanism. Prior to version 5.0.0, the partial-pipeline resume mechanism accepted `partial_token` as a bearer credential without binding it to the browser session that created it. Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim&amp;#39;s browser to resume that attacker-controlled flow. This could authenticate the victim&amp;#39;s browser as the attacker&amp;#39;s account. The issue affects applications using partial pipeline steps such as `mail_validation` or custom steps decorated with `@partial`. The issue has been fixed in version 5.0.0 by binding partial pipeline resumes to the originating browser session.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-57179</guid>
    </item>
    <item>
      <title>GHSA-vqg6-3fw6-j9jg — social-auth-core has a Session Fixation issue</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vqg6-3fw6-j9jg</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 partial-pipeline resume mechanism accepted `partial_token` as a bearer credential without binding it to the browser session that created it.&lt;/p&gt;
&lt;p&gt;Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim&amp;#39;s browser to resume that attacker-controlled flow. This could authenticate the victim&amp;#39;s browser as the attacker&amp;#39;s account.&lt;/p&gt;
&lt;p&gt;The issue affects applications using partial pipeline steps such as `mail_validation` or custom steps decorated with `@partial`.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue has been fixed by binding partial pipeline resumes to the originating browser session.&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/1816
* https://github.com/python-social-auth/social-docs/pull/444
* https://github.com/python-social-auth/social-app-django/pull/1009&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Applications that cannot upgrade immediately should disable resumable partial pipeline steps, including `mail_validation` and custom steps decorated with `@partial`.&lt;/p&gt;
&lt;p&gt;If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed.&lt;/p&gt;
&lt;p&gt;There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism.&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,…&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 partial-pipeline resume mechanism accepted `partial_token` as a bearer credential without binding it to the browser session that created it.&lt;/p&gt;
&lt;p&gt;Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim&amp;#39;s browser to resume that attacker-controlled flow. This could authenticate the victim&amp;#39;s browser as the attacker&amp;#39;s account.&lt;/p&gt;
&lt;p&gt;The issue affects applications using partial pipeline steps such as `mail_validation` or custom steps decorated with `@partial`.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue has been fixed by binding partial pipeline resumes to the originating browser session.&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/1816
* https://github.com/python-social-auth/social-docs/pull/444
* https://github.com/python-social-auth/social-app-django/pull/1009&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Applications that cannot upgrade immediately should disable resumable partial pipeline steps, including `mail_validation` and custom steps decorated with `@partial`.&lt;/p&gt;
&lt;p&gt;If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed.&lt;/p&gt;
&lt;p&gt;There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism.&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,…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vqg6-3fw6-j9jg</guid>
    </item>
    <item>
      <title>PYSEC-2026-4168 — social-auth-core has a Session Fixation issue</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-4168</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 partial-pipeline resume mechanism accepted `partial_token` as a bearer credential without binding it to the browser session that created it.&lt;/p&gt;
&lt;p&gt;Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim&amp;#39;s browser to resume that attacker-controlled flow. This could authenticate the victim&amp;#39;s browser as the attacker&amp;#39;s account.&lt;/p&gt;
&lt;p&gt;The issue affects applications using partial pipeline steps such as `mail_validation` or custom steps decorated with `@partial`.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue has been fixed by binding partial pipeline resumes to the originating browser session.&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/1816
* https://github.com/python-social-auth/social-docs/pull/444
* https://github.com/python-social-auth/social-app-django/pull/1009&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Applications that cannot upgrade immediately should disable resumable partial pipeline steps, including `mail_validation` and custom steps decorated with `@partial`.&lt;/p&gt;
&lt;p&gt;If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed.&lt;/p&gt;
&lt;p&gt;There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism.&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,…&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 partial-pipeline resume mechanism accepted `partial_token` as a bearer credential without binding it to the browser session that created it.&lt;/p&gt;
&lt;p&gt;Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim&amp;#39;s browser to resume that attacker-controlled flow. This could authenticate the victim&amp;#39;s browser as the attacker&amp;#39;s account.&lt;/p&gt;
&lt;p&gt;The issue affects applications using partial pipeline steps such as `mail_validation` or custom steps decorated with `@partial`.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue has been fixed by binding partial pipeline resumes to the originating browser session.&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/1816
* https://github.com/python-social-auth/social-docs/pull/444
* https://github.com/python-social-auth/social-app-django/pull/1009&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Applications that cannot upgrade immediately should disable resumable partial pipeline steps, including `mail_validation` and custom steps decorated with `@partial`.&lt;/p&gt;
&lt;p&gt;If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed.&lt;/p&gt;
&lt;p&gt;There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism.&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,…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-4168</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-57179</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-57179</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: python2.7, Ubuntu:Pro:14.04:LTS: python3.4, Ubuntu:Pro:14.04:LTS: python3.5, Ubuntu:Pro:16.04:LTS: python2.7, Ubuntu:Pro:16.04:LTS: python3.5, Ubuntu:Pro:18.04:LTS: python2.7, Ubuntu:Pro:18.04:LTS: python3.6, Ubuntu:Pro:18.04:LTS: python3.7, Ubuntu:Pro:18.04:LTS: python3.8, Ubuntu:Pro:20.04:LTS: python3.8 and 7 more&lt;/p&gt;
&lt;p&gt;Python Social Auth is a social authentication/registration mechanism. Prior to version 5.0.0, the partial-pipeline resume mechanism accepted `partial_token` as a bearer credential without binding it to the browser session that created it. Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim&amp;#39;s browser to resume that attacker-controlled flow. This could authenticate the victim&amp;#39;s browser as the attacker&amp;#39;s account. The issue affects applications using partial pipeline steps such as `mail_validation` or custom steps decorated with `@partial`. The issue has been fixed in version 5.0.0 by binding partial pipeline resumes to the originating browser session.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: python2.7, Ubuntu:Pro:14.04:LTS: python3.4, Ubuntu:Pro:14.04:LTS: python3.5, Ubuntu:Pro:16.04:LTS: python2.7, Ubuntu:Pro:16.04:LTS: python3.5, Ubuntu:Pro:18.04:LTS: python2.7, Ubuntu:Pro:18.04:LTS: python3.6, Ubuntu:Pro:18.04:LTS: python3.7, Ubuntu:Pro:18.04:LTS: python3.8, Ubuntu:Pro:20.04:LTS: python3.8 and 7 more&lt;/p&gt;
&lt;p&gt;Python Social Auth is a social authentication/registration mechanism. Prior to version 5.0.0, the partial-pipeline resume mechanism accepted `partial_token` as a bearer credential without binding it to the browser session that created it. Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim&amp;#39;s browser to resume that attacker-controlled flow. This could authenticate the victim&amp;#39;s browser as the attacker&amp;#39;s account. The issue affects applications using partial pipeline steps such as `mail_validation` or custom steps decorated with `@partial`. The issue has been fixed in version 5.0.0 by binding partial pipeline resumes to the originating browser session.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-57179</guid>
    </item>
  </channel>
</rss>
