PatchSiren cyber security CVE debrief
CVE-2026-57178 python-social-auth CVE debrief
CVE-2026-57178 debrief: Python Social Auth vulnerability allows unsigned data to be treated as verified VK identity, potentially allowing authentication as an arbitrary VK user ID. The `vk-app` backend in Python Social Auth accepted unsigned VK application callback data when the `auth_key` parameter was omitted. This issue affects applications using the `vk-app` backend prior to version 5.0.0. Defenders of applications using this backend should assess exposure and verify authentication mechanisms to prevent potential authentication as an arbitrary VK user ID.
- Vendor
- python-social-auth
- Product
- social-core
- CVSS
- HIGH 7.4
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-24
- Original CVE updated
- 2026-09-25
- Advisory published
- 2026-09-24
- Advisory updated
- 2026-09-25
Who should care
Defenders of applications using the `vk-app` backend in Python Social Auth should assess exposure and verify authentication mechanisms to prevent potential authentication as an arbitrary VK user ID. This includes operators, platform administrators, vulnerability management teams, and security teams responsible for ensuring the security of applications using this backend.
Why it matters
CVE-2026-57178 allows unsigned data to be treated as verified VK identity in Python Social Auth, impacting applications using the `vk-app` backend prior to version 5.0.0.
- Potential authentication as an arbitrary VK user ID
- Unsigned data treated as verified VK identity
- Verification of authentication mechanisms required
- Update to version 5.0.0 or later necessary for fix
Technical summary
The `vk-app` backend in Python Social Auth accepted unsigned VK application callback data when the `auth_key` parameter was omitted, potentially allowing authentication as an arbitrary VK user ID. This issue affects applications using the `vk-app` backend prior to version 5.0.0. The vulnerability allows unsigned data to be treated as verified VK identity, impacting applications using this backend. Defenders should assess exposure and verify authentication mechanisms to prevent potential authentication as an arbitrary VK user ID.
Defensive priority
Assess exposure and verify authentication mechanisms
Recommended defensive actions
- Assess exposure of applications using the `vk-app` backend
- Verify authentication mechanisms for VK identity
- Update to version 5.0.0 or later if vulnerable
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
Evidence notes
The CVE record and NVD entry provide details on the vulnerability in Python Social Auth. The issue affects applications using the `vk-app` backend prior to version 5.0.0. Evidence is limited to public CVE and NVD details. Defenders should verify authentication mechanisms and assess exposure of applications using the `vk-app` backend. The CVE Program and NVD provide official details on this vulnerability.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-57178 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-57178
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-57178 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-57178
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/python-social-auth/social-core/security/advisories/GHSA-3c93-f73f-qc9h
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.