Description
An issue was discovered in drf-jwt 1.15.x before 1.15.1. It allows attackers with access to a notionally invalidated token to obtain a new, working token via the refresh endpoint, because the blacklist protection mechanism is incompatible with the token-refresh feature. NOTE: drf-jwt is a fork of jpadilla/django-rest-framework-jwt, which is unmaintained.
Metrics
CVSS 3.1 9.1/10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| n/a | n/a | n/a |
References
- https://github.com/Styria-Digital/django-rest-framework-jwt/issues/36Issue Tracking, Third Party Advisory
- https://github.com/jpadilla/django-rest-framework-jwt/issues/484Issue Tracking, Third Party Advisory
- https://pypi.org/project/drf-jwt/1.15.1/#historyRelease Notes, Third Party Advisory
- https://github.com/Styria-Digital/django-rest-framework-jwt/issues/36Issue Tracking, Third Party Advisory
- https://github.com/jpadilla/django-rest-framework-jwt/issues/484Issue Tracking, Third Party Advisory
- https://pypi.org/project/drf-jwt/1.15.1/#historyRelease Notes, Third Party Advisory
Timeline
- Published
- Mar 15, 2020
- Last modified
- Jun 17, 2026
- NVD status
- Modified