<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Social-Auth-Core (&lt; 5.0.0) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/social-auth-core--5.0.0/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 24 Sep 2026 20:04:32 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/social-auth-core--5.0.0/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Authentication Bypass in social-auth-core VK App Backend</title><link>https://feed.craftedsignal.io/briefs/2026-09-social-auth-core-auth-bypass/</link><pubDate>Thu, 24 Sep 2026 20:04:32 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-09-social-auth-core-auth-bypass/</guid><description>The social-auth-core library fails to verify signatures in the vk-app backend when the auth_key parameter is missing, allowing attackers to impersonate arbitrary VK users.</description><content:encoded><![CDATA[<p>A vulnerability (CVE-2026-57178) exists in the social-auth-core library affecting the <code>vk-app</code> backend. When an application processes callback data from the VK platform, the library fails to enforce signature verification if the <code>auth_key</code> parameter is omitted from the request. This flaw allows an attacker to manipulate callback parameters such as <code>viewer_id</code>, <code>access_token</code>, <code>api_id</code>, and <code>api_result</code>. By crafting a malicious request without an <code>auth_key</code>, an attacker can inject arbitrary identity information, tricking the backend into authenticating them as any VK user. This vulnerability is specific to the <code>social_core.backends.vk.VKAppOAuth2</code> implementation. Defending against this requires upgrading to version 5.0.0 or later, or disabling the affected authentication backend entirely.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows for full authentication bypass and identity impersonation within any web application that relies on the <code>vk-app</code> backend for user login. An attacker can gain unauthorized access to victim accounts, access user-specific data, and perform actions on behalf of legitimate users. The vulnerability affects all users of social-auth-core versions prior to 5.0.0 utilizing the VK App OAuth2 backend.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade social-auth-core to version 5.0.0 or later to ensure the <code>auth_key</code> parameter is strictly required for signature verification.</li>
<li>If an immediate upgrade is not feasible, disable the vulnerable backend by removing <code>social_core.backends.vk.VKAppOAuth2</code> from the <code>SOCIAL_AUTH_AUTHENTICATION_BACKENDS</code> configuration in your application settings.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>authentication-bypass</category><category>web-vulnerability</category><category>python-social-auth</category></item></channel></rss>