Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to version 1.6.9, a JWK Header Injection vulnerability in authlib's JWS implementation allows an unauthenticated attacker to forge arbitrary JWT tokens that pass signature verification. When key=None is passed to any JWS deserialization function, the library extracts and uses the cryptographic key embedded in the attacker-controlled JWT jwk header field. An attacker can sign a token with their own private key, embed the matching public key in the header, and have the server accept the forged token as cryptographically valid — bypassing authentication and authorization entirely. This issue has been patched in version 1.6.9.
CVE-2026-27962
This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.1
- EG Score
- 9.1(low)
- EG Risk
- —
- EPSS
- 42.5%
- KEV
- Not listed
Published
March 16, 2026
Last Modified
July 20, 2026
Advisory Details (10)
Auto-updated Jun 30, 20262448164 – (CVE-2026-27962) CVE-2026-27962 authlib: Authlib: Authentication bypass due to JWK Header Injection vulnerability
https://bugzilla.redhat.com/show_bug.cgi?id=2448164JWS JWK Header Injection: Signature Verification Bypass · Advisory · authlib/authlib · GitHub
https://github.com/authlib/authlib/security/advisories/GHSA-wvwj-cvrp-7pv5v1.6.9
Patch available: authlib/authlib v1.6.9
https://github.com/authlib/authlib/releases/tag/v1.6.9commit a5d4b2d4c9e4 (authlib/authlib)
Patch available: authlib/authlib v1.6.9 (contains commit a5d4b2d4c9e4)
https://github.com/authlib/authlib/commit/a5d4b2d4c9e46bfa11c82f85fdc2bcc0b50ae681Vendor Advisories for CVE-2026-27962(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:24853Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.15.5
- RHSA-2026:19375Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.16.4
- RHSA-2026:7314Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.14.7
- RHSA-2026:5665Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.10.19
Patch Availability(4)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | quay/quay-rhel8:1780891395 | 2026-06-09 | redhat |
| redhat | quay/quay-rhel9:1779204086 | 2026-05-19 | redhat |
| redhat | quay/quay-rhel8:1775512163 | 2026-04-09 | redhat |
| redhat | quay/quay-rhel8:1773971077 | 2026-03-24 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| authlib | 0.1 ... 1.6.8 (56 versions) | 1.6.9 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 40× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-18 06:59 UTCOSV refresh
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
Show 15 moreShow fewer
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 04:38 UTCEG score recompute
- 2026-06-30 04:38 UTCVendor advisory
- 2026-06-30 04:31 UTCNVD updatefirst tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
Same CWE
10 shownCWE-347
Frequently asked(5)
What is CVE-2026-27962?
When was CVE-2026-27962 disclosed?
Is CVE-2026-27962 actively exploited?
What is the CVSS score of CVE-2026-27962?
How do I remediate CVE-2026-27962?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-27962
Is Your Infrastructure Affected by CVE-2026-27962?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.