VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

social-auth-core: vulnerability history, versions and safety

social-auth-core is a package in the PyPI ecosystem. Vulert records 11 vulnerabilities for it across 52 releases, from Sep 2026 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded H1 M5 U5
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
11 in the last 12 months

Most recent disclosure 15 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all social-auth-core vulnerabilities

Vulert verdict on social-auth-core 6.2.0 i

Updated on 23 Oct 2026

Good news: 6.2.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 11.

Package health score 66/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Stay on 6.2.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 6.2.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 6.2.0 — unaffected i
  • Vulnerabilities on record 11 over 1 year · 11 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 7.4 i
  • With no published fix 0 i
  • Depended on by 138 packages i
  • Stars 922 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for social-auth-core, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
6.2.0 20 Oct 2026 none BSD-3-Clause — Details →
6.1.1 10 Oct 2026 none BSD-3-Clause — Details →
6.1.0 08 Oct 2026 none BSD-3-Clause — Details →
6.0.0 06 Oct 2026 none BSD-3-Clause — Details →
5.2.0 30 Sep 2026 none BSD-3-Clause — Details →
5.1.1 18 Sep 2026 none BSD-3-Clause — Details →
5.1.0 06 Aug 2026 none BSD-3-Clause — Details →
5.0.2 26 Jun 2026 none BSD-3-Clause — Details →
5.0.1 24 Jun 2026 M1 BSD-3-Clause Yes Details →
5.0.0 23 Jun 2026 M1 BSD-3-Clause Yes Details →
4.9.1 30 Apr 2026 H1 M5 U5 BSD-3-Clause Yes Details →
4.9.0 29 Apr 2026 H1 M5 U5 BSD-3-Clause Yes Details →
4.8.7 23 Apr 2026 H1 M5 U5 BSD-3-Clause Yes Details →
4.8.6 20 Apr 2026 H1 M5 U5 BSD-3-Clause Yes Details →
4.8.5 10 Feb 2026 H1 M5 U5 BSD-3-Clause Yes Details →
4.8.4 10 Feb 2026 H1 M5 U5 BSD-3-Clause Yes Details →
4.8.3 18 Dec 2025 H1 M5 U5 BSD-3-Clause Yes Details →
4.8.2 18 Dec 2025 H1 M5 U5 BSD-3-Clause Yes Details →
4.8.1 09 Oct 2025 H1 M5 U5 BSD-3-Clause Yes Details →
4.8.0 07 Oct 2025 H1 M5 U5 BSD-3-Clause Yes Details →
4.7.0 27 Jun 2025 H1 M5 U5 BSD-3-Clause Yes Details →
4.6.1 28 Apr 2025 H1 M5 U5 BSD-3-Clause Yes Details →
4.6.0 25 Apr 2025 H1 M5 U5 BSD-3-Clause Yes Details →
4.5.6 13 Feb 2025 H1 M5 U5 non-standard Yes Details →
4.5.5 13 Feb 2025 H1 M5 U5 non-standard Yes Details →
4.5.4 25 Apr 2024 H1 M5 U5 non-standard Yes Details →
4.5.3 14 Feb 2024 H1 M5 U5 non-standard Yes Details →
4.5.2 26 Jan 2024 H1 M5 U5 non-standard Yes Details →
4.5.1 29 Nov 2023 H1 M5 U5 non-standard Yes Details →
4.5.0 31 Oct 2023 H1 M5 U5 non-standard Yes Details →
4.4.2 22 Apr 2023 H1 M5 U5 non-standard Yes Details →
4.4.1 30 Mar 2023 H1 M5 U5 non-standard Yes Details →
4.4.0 15 Mar 2023 H1 M5 U5 non-standard Yes Details →
4.3.0 13 Jun 2022 H1 M5 U5 non-standard Yes Details →
4.2.0 17 Jan 2022 H1 M5 U5 non-standard Yes Details →
4.1.0 05 Mar 2021 H1 M5 U5 non-standard Yes Details →
4.0.3 12 Jan 2021 H1 M5 U5 non-standard Yes Details →
3.4.0 11 Jan 2021 H1 M5 U5 non-standard Yes Details →
4.0.2 10 Jan 2021 H1 M5 U5 non-standard Yes Details →
3.3.3 02 Apr 2020 H1 M5 U5 non-standard Yes Details →
3.3.2 25 Mar 2020 H1 M5 U5 non-standard Yes Details →
3.3.1 25 Mar 2020 H1 M5 U5 non-standard Yes Details →
3.3.0 17 Mar 2020 H1 M5 U5 non-standard Yes Details →
3.2.0 30 May 2019 H1 M5 U5 non-standard Yes Details →
3.1.0 20 Feb 2019 H1 M5 U5 non-standard Yes Details →
3.0.0 14 Jan 2019 H1 M5 U5 non-standard Yes Details →
2.0.0 28 Oct 2018 H1 M5 U5 non-standard Yes Details →
1.7.0 20 Feb 2018 H1 M5 U5 non-standard Yes Details →
1.6.0 22 Dec 2017 H1 M5 U5 non-standard Yes Details →
1.5.0 28 Oct 2017 H1 M5 U5 non-standard Yes Details →
1.4.0 09 Jun 2017 H1 M5 U5 non-standard Yes Details →
1.3.0 06 May 2017 H1 M5 U5 non-standard Yes Details →
1.2.0 10 Feb 2017 H1 M5 U5 non-standard Yes Details →
1.1.0 31 Jan 2017 H1 M5 U5 non-standard Yes Details →
1.0.1 23 Jan 2017 H1 M5 U5 non-standard Yes Details →
1.0.0 22 Jan 2017 H1 M5 U5 non-standard Yes Details →
0.2.1 31 Dec 2016 H1 M5 U5 non-standard Yes Details →
0.2.0 31 Dec 2016 H1 M5 U5 non-standard Yes Details →
0.1.0 28 Dec 2016 H1 M5 U5 non-standard Yes Details →
0.0.1 27 Nov 2016 H1 M5 U5 non-standard Yes Details →

All 60 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 11

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 11 of the 11 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for social-auth-core

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-57178: social-auth-core - VK App Backend Accepts Unsigned Callback Data 7.4 high 5.0.0 24 Sep 2026
CVE-2026-57178: social-auth-core - VK App Backend Accepts Unsigned Callback Data 7.4 high 5.0.0 01 Oct 2026
CVE-2026-57176: social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend 6.8 medium 5.0.0 24 Sep 2026
CVE-2026-57176: social-auth-core Account Takeover Vulnerability via Vend Backend Identity Binding Flaw 6.8 medium 5.0.0 01 Oct 2026
CVE-2026-62322: social-auth-core - Login CSRF in LINE backend due to Missing OAuth State Validation 6.5 medium 5.0.2 15 Oct 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About social-auth-core

Is social-auth-core safe to use?

Vulert records 11 vulnerabilities for social-auth-core in PyPI: 0 critical, 1 high, 5 medium and 0 low, plus 5 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is social-auth-core's Vulert package health score?

Vulert scores social-auth-core 66/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of social-auth-core affected?

No. 6.2.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does social-auth-core have?

11 vulnerabilities are recorded for social-auth-core in the PyPI ecosystem: 0 critical, 1 high, 5 medium and 0 low, plus 5 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new social-auth-core vulnerabilities disclosed?

11 vulnerabilities were recorded for social-auth-core in the last 12 months, and the oldest entry in this database dates to 24 Sep 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of social-auth-core are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor social-auth-core for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the social-auth-core version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.