Is authlib 1.9 vulnerable?
PyPI · 10 releases from 1.9.0 to 1.9.9 · latest authlib is 1.9.9 · checked 18 Nov 2026
No known advisories in the last release
authlib 1.9.9, the last 1.9 release, has no known advisories. 2 advisories affect earlier 1.9.x releases, so update to 1.9.9.
pip install 'authlib>=1.9.9'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
Fixed within 1.9.x, affecting earlier releases
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
Every authlib 1.9.x release
Affected: 1.9.0. 1.9.1 and later are not affected.
| Version | Known advisories |
|---|---|
| authlib 1.9.9 | None |
| authlib 1.9.8 | None |
| authlib 1.9.7 | None |
| authlib 1.9.6 | None |
| authlib 1.9.5 | None |
| authlib 1.9.4 | None |
| authlib 1.9.3 | None |
| authlib 1.9.2 | None |
| authlib 1.9.1 | None |
| authlib 1.9.0 | CVE-2026-116672, CVE-2026-114616 |
Which of your client projects are still on authlib 1.9?
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.