VU#762428: Authlib library contains a signature‑verification bypass vulnerability
Affects authlibSource CERT/CC
Not known to be exploited · CVSS 9.8 Critical.
Data as of 17 Nov 2026, 20:42 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 9.8 |
|---|
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 28 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIauthlibpkg:pypi/authlibOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users are advised to monitor the Authlib project's GitHub repository for updates and apply the latest version once a fix is released. Until then, users should consider alternative verification methods or additional validation layers to mitigate risk.
Description
Authlib versions up to and including 1.7.2 contain a signature-verification bypass vulnerability in their JSON Web Signature (JWS) handling. The vulnerability allows attackers to supply JWS objects with an empty "signatures" array, which Authlib mistakenly treats as verified without performing signature checks. This enables attackers to forge arbitrary authenticated payloads without possessing any signing keys, potentially leading to authentication bypass, privilege escalation, and message integrity compromise. No official patch is currently available, and users should monitor the project's GitHub repository for updates.