{"action":"Upgrade django-allauth to 65.13.0 or later.","affected":[{"fixed":"65.13.0","introduced":"0"}],"component":"django-allauth","cve_ids":["CVE-2025-65430"],"ecosystem":"PyPI","epss":0.00165,"exploited":false,"fixed_versions":["65.13.0"],"ghsa_id":"GHSA-qhmc-3mvr-f2j4","id":"tcs_01M5KGNN1446TG4KHTXTBGMFRR","modified_at":"2026-06-10T17:00:47.431599720Z","published_at":"2025-12-15T14:15:57.017Z","references":["https://osv.dev/vulnerability/PYSEC-2025-110","https://allauth.org/news/2025/10/django-allauth-65.13.0-released/","https://github.com/advisories/GHSA-qhmc-3mvr-f2j4"],"severity":{"label":"medium","score":5.4},"sources":[{"source":"osv","source_id":"PYSEC-2025-110","url":"https://osv.dev/vulnerability/PYSEC-2025-110"}],"summary":"An issue was discovered in allauth-django before 65.13.0. IdP: marking a user as is_active=False after having handed tokens for that user while the account was still active had no effect. Fixed the ac"}