# CVE-2026-16206: django-oauth django-oauth-toolkit oauth2_validators.py _load_id_token session expiration

> Attackers can bypass session expiration controls in django-oauth-toolkit, potentially maintaining unauthorized access.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-j4j7-8j5c-5hxw, openSUSE-SU-2026:11624-1

## What is CVE-2026-16206?

CVE-2026-16206 is a medium-severity vulnerability in django-oauth-toolkit, published on 19 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in django-oauth django-oauth-toolkit 3.3.0. This issue affects the function _load_id_token of the file oauth2_provider/oauth2_validators.py. The manipulation leads to session expiration. The attack can be initiated remotely. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2026-16206?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `python-django-oauth-toolkit` | openSUSE:Tumbleweed | All versions | 3.4.1-1.1 |

## How do I fix CVE-2026-16206?

No fix published yet.

## Is CVE-2026-16206 being exploited?

There is no known exploitation of CVE-2026-16206 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16206 and fix it if it is affected.

What it is: CVE-2026-16206 is a medium-severity vulnerability in django-oauth-toolkit, published on 19 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16206 in the wild and no public exploit code.

Affected product: django-oauth-toolkit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16206/ (Markdown: https://insights.sbomify.com/CVE-2026-16206/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16206
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16206
- OSV: https://osv.dev/vulnerability/CVE-2026-16206

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16206/
Summaries are generated and may contain mistakes; the official description above is the record.