# CVE-2026-114619: Authlib: OpenID implicit grant checks raw scope instead of allowed scope before issuing ID tokens


- **Severity:** Medium 4.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/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-114619, ECHO-72c7-353f-8dfa, GHSA-q686-2qmg-hqc7, MINI-9688-r4gw-33cc, UBUNTU-CVE-2026-114619

## What is CVE-2026-114619?

CVE-2026-114619 is a medium-severity vulnerability in authlib, published on 22 Oct 2026. 

### Official description

Authlib is a Python library which builds OAuth and OpenID Connect servers. Prior to 1.9.0, OpenIDImplicitGrant.validate_authorization_request() checks the client-controlled raw request.payload.scope for openid after the parent grant has filtered allowed scopes into request.scope. A registered client permitted an ID token response type but not the openid scope can add openid to the request, obtain user consent, and receive a signed ID token containing the user's subject and allowed profile claims. Authorization code flow and deployments that allow openid for every client permitted an ID token response are not affected. In authlib/oidc/core/grants/implicit.py, OpenIDImplicitGrant.validate_authorization_request() checks request.payload.scope instead of the filtered request.scope. This issue is fixed in version 1.9.0.

Weakness: CWE-863 (Incorrect Authorization)

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

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


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

Products: Authlib Authlib.

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

Upgrade authlib to 1.9.0 or later.

## Is CVE-2026-114619 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114619 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-114619 and fix it if it is affected.

What it is: CVE-2026-114619 is a medium-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-114619 exists.

Affected packages and fixed versions:
- authlib (PyPI): affected all versions; fixed in 1.9.0
- authlib (PyPI): affected all versions; fixed in 1.9.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-114619/ (Markdown: https://insights.sbomify.com/CVE-2026-114619/index.md)
```

## Sources

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

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