Authlib
13 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Authlib, a product in the oss libraries space. Use it to gauge the current risk picture and drill into individual advisories.
Authlib CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 1 |
| 2025-10 | 2 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 1 |
| 2026-02 | 0 |
| 2026-03 | 4 |
| 2026-04 | 2 |
| 2026-05 | 1 |
| 2026-06 | 1 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 13 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- Critical2
- High4
- Medium6
Latest CVEs
The 13 most recently published vulnerabilities affecting Authlib.
- CVE-2026-41479Authlib OAuth 2.0 authorization endpoint open redirects to attacker-controlled redirect_uri on unsupported response_type5.4
- CVE-2026-44681Authlib: Open Redirect in Authlib OIDC Implicit/Hybrid Authorization6.1
- CVE-2026-41425Authlib: Cross-site request forging when using cache5.4
- GHSA-jj8c-mmj3-mmgvAuthlib: Cross-site request forging when using cache—
- CVE-2026-28498Authlib: Fail-Open Cryptographic Verification in OIDC Hash Binding7.5
- CVE-2026-28490Authlib Vulnerable to JWE RSA1_5 Bleichenbacher Padding Oracle6.5
- CVE-2026-27962Authlib JWS JWK Header Injection: Signature Verification Bypass9.1
- CVE-2026-28802Authlib: Setting `alg: none` and a blank signature appears to bypass signature verification9.8
- CVE-2025-68158Authlib: 1-click Account Takeover5.7
- CVE-2025-62706Authlib : JWE zip=DEF decompression bomb enables DoS6.5
- CVE-2025-61920Authlib is vulnerable to Denial of Service via Oversized JOSE Segments7.5
- CVE-2025-59420Authlib: JWS/JWT accepts unknown crit headers (RFC violation → possible authz bypass)7.5
- CVE-2024-37568lepture Authlib before 1.3.1 has algorithm confusion with asymmetric public keys. Unless an algorithm is specified in a jwt.decode call, HMAC verification is allowed with any asymmetric public key....7.5
Product grouping is registry-driven, with AI assist and human review. How it works