# 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...

Advisory record · `GHSA-qhmc-3mvr-f2j4`

- **Identifiers:** `GHSA-qhmc-3mvr-f2j4` · `CVE-2025-65430` · `PYSEC-2025-110`
- **State:** Confirmed
- **Severity:** CVSS 5.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-613](https://cwe.mitre.org/data/definitions/613.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 15 Dec 2025
- **Updated:** 10 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 15 Dec 2025, 14:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `django-allauth` (PyPI): affected `<65.13.0`; fixed in `65.13.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Versions of django-allauth before 65.13.0 are affected. When the identity provider (IdP) functionality is used, setting a user's is_active flag to False after tokens were already issued for that user while the account was active had no effect, so the tokens kept working. The source gives few details on the exact conditions or who could exploit this. Upgrade to django-allauth 65.13.0 or later, where access and refresh tokens are rejected once the user is deactivated.

Written 10 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.4 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`, from OSV

- **CISA KEV:** Not listed.
- **EPSS:** 0.0018, the 7th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 15 Dec 2025. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-qhmc-3mvr-f2j4](https://github.com/advisories/GHSA-qhmc-3mvr-f2j4)
- [OSV: GHSA-qhmc-3mvr-f2j4](https://osv.dev/vulnerability/GHSA-qhmc-3mvr-f2j4)
- <https://allauth.org/news/2025/10/django-allauth-65.13.0-released/>
- <https://github.com/advisories/GHSA-qhmc-3mvr-f2j4>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-qhmc-3mvr-f2j4>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-qhmc-3mvr-f2j4/>. Everything for agents: <https://agentprime.io/llms.txt>.
