Is authlib 1.8 vulnerable?
PyPI · 1 release from 1.8.0 to 1.8.0 · latest authlib is 1.9.9 · checked 18 Nov 2026
Yes: 8 known advisories
Yes. authlib 1.8.0, the last 1.8 release, is affected by 8 known security advisories (1 critical, 3 high, 4 medium), including CVE-2026-96760, CVE-2026-116672, CVE-2026-114616. Upgrade to 1.9.1 or later to fix all of them.
pip install 'authlib>=1.9.1'Is your project on an affected authlib?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting authlib 1.8.0
Authlib RFC 7592 examples omit registration-access-token client binding
- Affected
- >=0.15 <1.9.1
- Fixed in
- 1.9.1
Authlib accepts an empty HMAC key, allowing JWS/JWT signature forgery (HS256/HS384/HS512)
- Affected
- <1.9.1
- Fixed in
- 1.9.1
Authlib: Unvalidated request_uri fetch in JWT-secured authorization request (JAR) leading to SSRF
- Affected
- >=1.6.0 <1.9.0
- Fixed in
- 1.9.0
Authlib: ID token can disable its own nonce validation via the nonce_supported claim
- Affected
- <1.9.0
- Fixed in
- 1.9.0
Authlib: Default JWT bearer grant accepts assertions for the wrong audience
- Affected
- <1.9.0
- Fixed in
- 1.9.0
Authlib: OpenID implicit grant checks raw scope instead of allowed scope before issuing ID tokens
- Affected
- <1.9.0
- Fixed in
- 1.9.0
Authlib incomplete algorithm-confusion fix permits HMAC forgery with prefixed public keys
- Affected
- >=1.3.1 <1.9.0
- Fixed in
- 1.9.0
Authlib: empty signatures validation in JWS JSON deserialization
- Affected
- <1.9.0
- Fixed in
- 1.9.0
Which of your client projects are still on authlib 1.8?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact authlib version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other authlib versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.