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.
CVE-2026-16206
Score 6.3 from GitHub Security Advisory published 2026-07-19. a secondary CVSS source baseline 6.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity63% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 27.5%
- KEV
- Not listed
Published
July 19, 2026
Last Modified
July 20, 2026
Advisory Details (2)
Auto-updated Jul 19, 2026Default token lifetime settings allow indefinite refresh tokens and expired ID tokens for RP logout · Issue #1715 · django-oauth/django-oauth-toolkit · GitHub
https://github.com/django-oauth/django-oauth-toolkit/issues/1715GitHub - django-oauth/django-oauth-toolkit: OAuth2 goodies for the Djangonauts! · GitHub
https://github.com/django-oauth/django-oauth-toolkit/Vendor Advisories for CVE-2026-16206(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:49 UTCEG score recompute
- 2026-07-20 17:49 UTCGHSA enrichment
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 04:23 UTCEG score recompute
- 2026-07-19 04:23 UTCGHSA enrichment
- 2026-07-19 02:28 UTCEG score recompute
- 2026-07-19 02:27 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-613
Frequently asked(5)
What is CVE-2026-16206?
When was CVE-2026-16206 disclosed?
Is CVE-2026-16206 actively exploited?
What is the CVSS score of CVE-2026-16206?
How do I remediate CVE-2026-16206?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16206
Is Your Infrastructure Affected by CVE-2026-16206?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.