Authentication bypass via default unsigned JWT acceptance
Published Mar 6, 2026 · Updated Mar 6, 2026
Improper JWT signature verification in Authlib 1.6.5 through 1.6.6 allows remote attackers to forge accepted tokens without a signature. The module-level authlib.jose.jwt instance registered the JWS none algorithm by default, so jwt.decode accepted an alg:none token with an empty signature. Exploitation requires an application to use that default decoder for authentication or authorization, enabling unauthorized access or actions under attacker-chosen claims.
Summary
What happened
Improper JWT signature verification in Authlib 1.6.5 through 1.6.6 allows remote attackers to forge accepted tokens without a signature. The module-level authlib.jose.jwt instance registered the JWS none algorithm by default, so jwt.decode accepted an alg:none token with an empty signature. Exploitation requires an application to use that default decoder for authentication or authorization, enabling unauthorized access or actions under attacker-chosen claims.
The record
- CVE
- CVE-2026-28802
- Published
- Mar 6, 2026
- Updated
- Mar 6, 2026
- Vendor
- Authlib
- Product
- Authlib
- Classifications
- CWE-347, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 6, 2026CVE publishedPublication date reported by the CVE source.
- Mar 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.6.5, < 1.6.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Unsigned alg:none JWT proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo