# CVE-2026-114614: Authlib: is_secure_transport() loopback exemption can be bypassed with a userinfo component, allowing cleartext-HTTP URLs to non-loopback hosts


- **Severity:** Low 2.6 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-114614, ECHO-4dee-6cb2-c9e4, GHSA-jj7h-c3hg-m23x, MINI-64x4-p8x7-g63r, MINI-9mg4-g9mh-46cw, UBUNTU-CVE-2026-114614

## What is CVE-2026-114614?

CVE-2026-114614 is a low-severity vulnerability in authlib, published on 22 Oct 2026. 

### Official description

Authlib is a Python library which builds OAuth and OpenID Connect servers. From 0.13 until 1.8.0, authlib.common.security.is_secure_transport() uses a textual prefix comparison for loopback HTTP exemptions, so a URL whose userinfo begins with a loopback host can be accepted even when its parsed host is an external non-loopback system. An external party able to supply a URL to OIDC RP-Initiated Logout registration, authorization-server metadata validation, or another call site can bypass the TLS-required guard and cause cleartext redirection or acceptance of cleartext endpoints. The issue does not bypass redirect URI exact matching and does not by itself forge tokens or authenticate users. The vulnerable authlib.common.security.is_secure_transport() implementation in authlib/common/security.py misinterprets the userinfo component before OIDC RP-Initiated Logout dynamic client registration and other consumers enforce transport security. This issue is fixed in version 1.8.0.

Weakness: CWE-693 (Protection Mechanism Failure), CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-114614?

2 open source packages ship an affected version, including authlib. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `authlib` | PyPI | All versions | 1.8.0 |
| `authlib` | PyPI | All versions | 1.8.0 |

Products: Authlib Authlib.

## How do I fix CVE-2026-114614?

Upgrade authlib to 1.8.0 or later.

## Is CVE-2026-114614 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114614 exists.

## Other vulnerabilities in authlib

- [CVE-2026-27962](https://insights.sbomify.com/CVE-2026-27962/): Authlib JWS JWK Header Injection: Signature Verification Bypass (critical 9.1)
- [CVE-2026-28490](https://insights.sbomify.com/CVE-2026-28490/): Authlib Vulnerable to JWE RSA1_5 Bleichenbacher Padding Oracle (high 8.3)
- [CVE-2026-28498](https://insights.sbomify.com/CVE-2026-28498/): Authlib: Fail-Open Cryptographic Verification in OIDC Hash Binding (high 8.2)
- [CVE-2026-28802](https://insights.sbomify.com/CVE-2026-28802/): Authlib: Setting `alg: none` and a blank signature appears to bypass signature verification (high 7.7)
- [CVE-2025-61920](https://insights.sbomify.com/CVE-2025-61920/): Authlib is vulnerable to Denial of Service via Oversized JOSE Segments (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114614 and fix it if it is affected.

What it is: CVE-2026-114614 is a low-severity vulnerability in authlib, published on 22 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114614 exists.

Affected packages and fixed versions:
- authlib (PyPI): affected all versions; fixed in 1.8.0
- authlib (PyPI): affected all versions; fixed in 1.8.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-114614/ (Markdown: https://insights.sbomify.com/CVE-2026-114614/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114614
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114614
- OSV: https://osv.dev/vulnerability/CVE-2026-114614

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-114614/
Summaries are generated and may contain mistakes; the official description above is the record.