Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Authlib versions before 1.3.1 are vulnerable to algorithm confusion when verifying JSON Web Tokens with asymmetric public keys. If the algorithm is not specified in a jwt.decode call, HMAC verification is accepted using the public key, so an attacker who can present a crafted token may be able to forge tokens that pass verification. Upgrade authlib to version 1.3.1 or later. Until then, specify the expected algorithm explicitly in every jwt.decode call.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | ADP (CISA-ADP) |
- CISA KEV Not listed.
- EPSS 0.0039, the 33rd percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.