CVE-2025-59420: Authlib: JWS/JWT accepts unknown crit headers (RFC violation → possible authz bypass)
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: authlib authlib 1.6.4.
Low priority for now. Upgrade to authlib authlib 1.6.4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 22, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- CWE-345
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| authlib | authlib | cpe:2.3:a:authlib:authlib |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
authlib authlib
- < 1.6.4affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- authlib authlibbefore 1.6.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | python-authlib | before 0.15.4-1+deb11u1 | 0.15.4-1+deb11u1 |
| Debian:12 | python-authlib | before 1.2.0-1+deb12u1 | 1.2.0-1+deb12u1 |
| Debian:13 | python-authlib | before 1.6.0-1+deb13u1 | 1.6.0-1+deb13u1 |
| Debian:14 | python-authlib | before 1.6.4-1 | 1.6.4-1 |
| PyPI | authlib | before 1.6.4 | 1.6.4 |
Same product
authlib: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-104056Authlib version 1.7.2 and below contains a vulnerability where discovery JSON metadata is cached without validation or issuer-origin…39Monitor
- CVE-2026-96760Authlib library contains a signature‑verification bypass vulnerability39Monitor
- CVE-2026-114616Authlib accepts an empty HMAC key, allowing JWS/JWT signature forgery (HS256/HS384/HS512)36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-37568Jun 9, 2024 · lepture Authlib before 1.3.1 has algorithm confusion with asymmetric public keys.30Monitor
- Later →CVE-2025-61920Oct 10, 2025 · Authlib is vulnerable to Denial of Service via Oversized JOSE Segments30Monitor
- Later →CVE-2025-62706Oct 22, 2025 · Authlib : JWE zip=DEF decompression bomb enables DoS26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| authlib authlib | 1.6.4 · description | Vendor (CNA) |
| debian:python-authlib | 1.2.0-1+deb12u1 · Debian:12 | Package registry (OSV) |
| PyPI:authlib | 1.6.4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-104056374 days apartAuthlib version 1.7.2 and below contains a vulnerability where discovery JSON metadata is cached without validation or issuer-origin…39Monitor
Not on record for this CVE: EPSS history · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-345 · Insufficient Verification of Data AuthenticityCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- JSON Hijacking (aka JavaScript Hijacking)CAPEC-111likelihood: High · High
- Cache PoisoningCAPEC-141likelihood: High · High
- DNS Cache PoisoningCAPEC-142likelihood: High · High
- Content SpoofingCAPEC-148likelihood: Medium · Medium
- Spoofing of UDDI/ebXML MessagesCAPEC-218Medium
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.