OIDC token integrity bypass via fail-open hash verification
Published Mar 16, 2026 · Updated Mar 16, 2026
OIDC ID Token validation in Authlib before 1.6.9 allows remote attackers to bypass at_hash and c_hash integrity checks. The _verify_hash function treats the None returned by create_half_hash for an unsupported alg value as success instead of rejecting the hash comparison. Exploitation requires an application to validate attacker-supplied OIDC ID Tokens containing hash claims and an unsupported algorithm; successful validation accepts a forged token binding.
Summary
What happened
OIDC ID Token validation in Authlib before 1.6.9 allows remote attackers to bypass at_hash and c_hash integrity checks. The _verify_hash function treats the None returned by create_half_hash for an unsupported alg value as success instead of rejecting the hash comparison. Exploitation requires an application to validate attacker-supplied OIDC ID Tokens containing hash claims and an unsupported algorithm; successful validation accepts a forged token binding.
The record
- CVE
- CVE-2026-28498
- Published
- Mar 16, 2026
- Updated
- Mar 16, 2026
- Vendor
- Authlib
- Product
- Authlib
- Classifications
- CWE-354, CWE-573
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 16, 2026CVE publishedPublication date reported by the CVE source.
- Mar 16, 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.9
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
- GHSA-m344-f55w-2m6j OIDC hash-bypass 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