CVE-2020-10594
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn drf-jwt versions before 1.15.1, the token blacklist mechanism that should invalidate revoked tokens is bypassed when attackers use the token refresh endpoint. An attacker possessing a token that has been revoked (e.g., after password change or logout) can still obtain a new valid token by calling the refresh endpoint, because the blacklist check is not properly enforced during the refresh operation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.15.0, < 1.15.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed drf-jwt versionRun 'pip show drf-jwt' or check your requirements file for the drf-jwt versionAffected if The installed version is >= 1.15.0 and < 1.15.1
-
Verify token blacklist is enabledCheck your Django settings.py for REST_FRAMEWORK_JWT configuration and confirm BLACKLIST_ENABLED is set to TrueAffected if Blacklist is enabled and the installed version is in the affected range
-
Confirm blacklist app is in INSTALLED_APPSCheck that 'rest_framework_jwt.blacklist' is listed in INSTALLED_APPS in settings.pyAffected if The blacklist app is installed and the version is affected
-
Check if refresh endpoint is exposedReview your URL routing for '/jwt/refresh/' or similar refresh endpoint pathsAffected if The refresh endpoint is accessible and drf-jwt version is in the affected range
You are affected if drf-jwt version is 1.15.0 and the token blacklist is enabled with the refresh endpoint accessible, allowing revoked tokens to be refreshed into new valid tokens.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.15.1
Upgrade drf-jwt to version 1.15.1 or later which contains the fix. If immediate upgrade is not possible, consider temporarily disabling the refresh endpoint or implementing additional server-side validation to block refresh attempts using blacklisted tokens.
drf-jwt version 1.15.1
- Check your current drf-jwt version by running: pip show drf-jwt or checking your requirements file
- Upgrade to the fixed version 1.15.1 by running: pip install drf-jwt==1.15.1
- After upgrading, verify the blacklist mechanism works correctly with token refresh by testing the refresh endpoint with a blacklisted token
- Ensure your application still issues and validates tokens correctly after the upgrade
- Review your application's authentication flow to confirm the blacklist protection is now properly enforced on the refresh endpoint
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10594 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-10594 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data