authlib vulnerabilities
The ultimate Python library in building OAuth and OpenID Connect servers and clients.
- Registry
- PyPI
- Latest
- 1.9.9
- License
- BSD-3-Clause
21 known advisories
The latest version, 1.9.9, is not affected by any of them. Projects on older versions may be.
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
Security advisories for authlib
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: is_secure_transport() loopback exemption can be bypassed with a userinfo component, allowing cleartext-HTTP URLs to non-loopback hosts
- Affected
- <1.8.0
- Fixed in
- 1.8.0
Authlib: empty signatures validation in JWS JSON deserialization
- Affected
- <1.9.0
- Fixed in
- 1.9.0
Authlib OAuth 2.0 has Open Redirect in Authorization API that allows attacker-controlled redirect_uri through unsupported response_type
- Affected
- <1.6.10 · >=1.7.0 <1.7.1
- Fixed in
- 1.6.10, 1.7.1
Authlib OIDC Implicit/Hybrid Authorization Vulnerable to Open Redirect
- Affected
- >=1.7.0 <1.7.1 · <1.6.12
- Fixed in
- 1.6.12, 1.7.1
Authlib: Cross-site request forging when using cache
- Affected
- <1.6.11
- Fixed in
- 1.6.11
Authlib: Fail-Open Cryptographic Verification in OIDC Hash Binding
- Affected
- <1.6.9
- Fixed in
- 1.6.9
Authlib Vulnerable to JWE RSA1_5 Bleichenbacher Padding Oracle
- Affected
- <1.6.9
- Fixed in
- 1.6.9
Authlib JWS JWK Header Injection: Signature Verification Bypass
- Affected
- <1.6.9
- Fixed in
- 1.6.9
Authlib: Setting `alg: none` and a blank signature appears to bypass signature verification
- Affected
- >=1.6.5 <1.6.7
- Fixed in
- 1.6.7
Authlib has 1-click Account Takeover vulnerability
- Affected
- >=1.0.0 <1.6.6
- Fixed in
- 1.6.6
Authlib : JWE zip=DEF decompression bomb enables DoS
- Affected
- <1.6.5
- Fixed in
- 1.6.5
Authlib is vulnerable to Denial of Service via Oversized JOSE Segments
- Affected
- <1.6.5
- Fixed in
- 1.6.5
Authlib: JWS/JWT accepts unknown crit headers (RFC violation → possible authz bypass)
- Affected
- <1.6.4
- Fixed in
- 1.6.4
Authlib has algorithm confusion with asymmetric public keys
- Affected
- <1.3.1
- Fixed in
- 1.3.1
Is your authlib version vulnerable?
- authlib 1.9No known advisories in 1.9.9
- authlib 1.88 advisories in 1.8.0
- authlib 1.79 advisories in 1.7.2
- authlib 1.69 advisories in 1.6.12
- authlib 1.518 advisories in 1.5.2
- authlib 1.418 advisories in 1.4.1
- authlib 0.1517 advisories in 0.15.6
- authlib 0.1416 advisories in 0.14.3
- authlib 0.1316 advisories in 0.13.0
- authlib 0.1216 advisories in 0.12.1
- authlib 0.1116 advisories in 0.11.0
- authlib 0.1016 advisories in 0.10.0
Which of your client projects still run an old authlib?
NPMscan reads the requirements.txt, poetry.lock, uv.lock and Pipfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other PyPI packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the PyPI registry.