CVE-2026-114614: authlib · Open Redirect
Affects authlibSource CVE Database V5
Not known to be exploited · CVSS 2.6 Low : upgrade to 1.8.0 when convenient.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.8.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade authlib to 1.8.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| authlibauthlib | Affected
| Fixed in
|
AI-suggested
Upgrade Authlib to version 1.8.0 or later, where this vulnerability is fixed. No other mitigation is required as the issue is resolved in the official fix.
Description
Authlib versions prior to 1.8.0 contain an open redirect vulnerability due to improper handling of loopback HTTP exemptions in the is_secure_transport() function. This flaw allows an attacker to bypass TLS requirements by supplying a URL with userinfo that begins with a loopback host, potentially causing cleartext redirection or acceptance of cleartext endpoints. The vulnerability does not affect redirect URI exact matching and does not enable token forgery or user authentication bypass. The issue is fixed in version 1.8.0.