Lookup for vulnerable packages by Package URL.
| Purl | pkg:pypi/authlib@1.6.4 |
| Type | pypi |
| Namespace | |
| Name | authlib |
| Version | 1.6.4 |
| Qualifiers |
|
| Subpath | |
| Is_vulnerable | true |
| Next_non_vulnerable_version | 1.6.11 |
| Latest_non_vulnerable_version | 1.6.11 |
| Affected_by_vulnerabilities |
| 0 |
| url |
VCID-hrf7-xz6n-efcg |
| vulnerability_id |
VCID-hrf7-xz6n-efcg |
| summary |
Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.6.11, there is no CSRF protection on the cache feature in authlib.integrations.starlette_client.OAuth. This vulnerability is fixed in 1.6.11. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2026-41425, GHSA-jj8c-mmj3-mmgv, PYSEC-2026-25
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-hrf7-xz6n-efcg |
|
|
| Fixing_vulnerabilities |
| 0 |
| url |
VCID-f8jg-a3bd-x7ax |
| vulnerability_id |
VCID-f8jg-a3bd-x7ax |
| summary |
Authlib: JWS/JWT accepts unknown crit headers (RFC violation → possible authz bypass)
Authlib’s JWS verification accepts tokens that declare unknown critical header parameters (`crit`), violating RFC 7515 “must‑understand” semantics. An attacker can craft a signed token with a critical header (for example, `bork` or `cnf`) that strict verifiers reject but Authlib accepts. In mixed‑language fleets, this enables split‑brain verification and can lead to policy bypass, replay, or privilege escalation. |
| references |
|
| fixed_packages |
|
| aliases |
CVE-2025-59420, GHSA-9ggr-2464-2j32
|
| risk_score |
null |
| exploitability |
null |
| weighted_severity |
null |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-f8jg-a3bd-x7ax |
|
|
| Risk_score | null |
| Resource_url | http://public2.vulnerablecode.io/packages/pkg:pypi/authlib@1.6.4 |