Django Rest Framework jwt allows obtaining new token from notionally invalidated token

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2020-10594: 1.62% estimated exploitation activity in the next 30 days; percentile 76.03 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

5 Jun 2020, 16:09 UTC

Last modified by the source

21 Feb 2025, 05:30 UTC

Source last checked

26 Oct 2026, 13:17 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-fpjm-rp2g-3r4c

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-fpjm-rp2g-3r4c

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-10594

Advisory: Django Rest Framework jwt allows obtaining new token from notionally invalidated token
IDs: CVE-2020-10594, GHSA-fpjm-rp2g-3r4c
Record: https://patchnext.com/advisories/cve-2020-10594 (revision 3, source checked 26 Oct 2026, 13:17 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: drf-jwt 1.15.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI drf-jwt: affected >= 1.15.0, < 1.15.1; fixed in 1.15.1

## Suggested inspection (read-only)
- `python -m pip show drf-jwt`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on drf-jwt.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-fpjm-rp2g-3r4c (OSV record GHSA-fpjm-rp2g-3r4c lists affected ranges: PyPI drf-jwt >=1.15.0 <1.15.1 (fixed))
- Verified: https://github.com/advisories/GHSA-fpjm-rp2g-3r4c (GitHub-reviewed advisory GHSA-fpjm-rp2g-3r4c lists affected ranges: PyPI drf-jwt >=1.15.0 <1.15.1)

Commands are suggestions: review each one before running it.