Authlib: JWS/JWT accepts unknown crit headers (RFC violation → possible authz bypass)
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| authlib | authlib | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Authlib | Authlib | — |
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-4352-1 | python-authlib security update |
EUVD |
EUVD-2025-30790 | Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to version 1.6.4, 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. This issue has been patched in version 1.6.4. |
Github GHSA |
GHSA-9ggr-2464-2j32 | Authlib: JWS/JWT accepts unknown crit headers (RFC violation → possible authz bypass) |
Ubuntu USN |
USN-8065-1 | Authlib vulnerabilities |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.275% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:authlib:authlib:*:*:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Authlib
Authlib authlib |
|
| Vendors & Products |
Authlib
Authlib authlib |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to version 1.6.4, 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. This issue has been patched in version 1.6.4. | |
| Title | Authlib: JWS/JWT accepts unknown crit headers (RFC violation → possible authz bypass) | |
| Weaknesses | CWE-345 CWE-863 |
|
| References |
| |
| Metrics |
cvssV3_1
|