How severe is CVE-2025-61783?

No CVSS score has been assigned to CVE-2025-61783 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-61783?

CVE-2025-61783 affects the following packages: social-auth-app-django (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2025-61783?

Update social-auth-app-django to 5.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-61783 is resolved across your whole dependency graph.

How do I detect CVE-2025-61783 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for social-auth-app-django, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-61783 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2025-61783 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-61783 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-61783?

CVE-2025-61783 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 46th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-61783?

CVE-2025-61783 is classified as CWE-303 (CWE-303). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-61783 published, and has it been updated?

CVE-2025-61783 was published on October 9, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2025-61783 — social-auth-app-django

Fix: python-social-auth/social-app-django@10c80e2

CVE-2025-61783 is a CWE-303 vulnerability in social-auth-app-django. A fix is available for social-auth-app-django — see the affected versions and patch details below.

Python Social Auth - Django has unsafe account association

Also known asGHSA-wv4w-6qv2-qqfgPYSEC-2026-1932

Published

Oct 9, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-61783.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk+0.12%

Lower risk than most CVEs46th percentile — riskier than 46% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍social-auth-app-django

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Python Social Auth is a social authentication/registration mechanism. In versions prior to 5.6.0, upon authentication, the user could be associated by e-mail even if the associate_by_email pipeline was not included. This could lead to account compromise when a third-party authentication service does not validate provided e-mail addresses or doesn't require unique e-mail addresses. Version 5.6.0 contains a patch. As a workaround, review the authentication service policy on e-mail addresses; many will not allow exploiting this vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`social-auth-app-django`	all versions	5.6.0`pip install --upgrade 'social-auth-app-django==5.6.0'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for social-auth-app-django, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update social-auth-app-django to 5.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-61783 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This issue is rated Moderate rather than Important because exploitation depends on multiple external conditions and is limited in scope. The vulnerability does not introduce a direct code execution or privilege escalation vector within Python Social Auth itself; instead, it relies on insecure behavior from third-party…

Workaround published by Red Hat

No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability. To reduce the risk, administrators should restrict authentication to trusted identity providers that enforce verified and unique e-mail addresses, and ensure that the associate_by_email pipeline is disabled or tightly controlled. Limiting external providers and reviewing account-linking logic can effectively reduce the risk of unintended account association or takeover.

Source: Red Hat security advisory for CVE-2025-61783 (CC BY 4.0)

Frequently Asked Questions

Python Social Auth is a social authentication/registration mechanism. In versions prior to 5.6.0, upon authentication, the user could be associated by e-mail even if the `associate_by_email` pipeline was not included. This could lead to account compromise when a third-party authentication service does not validate provided e-mail addresses or doesn't require unique e-mail addresses. Version 5.6.0 contains a patch. As a workaround, review the authentication service policy on e-mail addresses; many will not allow exploiting this vulnerability.

O3 Security · Impact-Aware SCA

Is CVE-2025-61783 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works