Is CVE-2026-114619 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-114619 being exploited in the wild.

How severe is CVE-2026-114619?

Medium severity, with a CVSS score of 4.6, published 22 October 2026.

Which products and versions are affected?

Authlib before 1.9.0; authlib (PyPI) < 1.9.0, ECOSYSTEM:introduced=0,fixed=1.9.0.

Is there a fix for CVE-2026-114619?

Yes. authlib (PyPI): upgrade to 1.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-114619 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-114619?

Check whether you run Authlib or authlib (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-114619: Authlib OpenID Connect scope validation bypass

Q: Is there a fix for CVE-2026-114619?

Yes. authlib (PyPI): upgrade to 1.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-114619 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-114619?

Check whether you run Authlib or authlib (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-114619 · Severity: medium · CVSS 4.6 · Published 2026-10-22

Authlib is a Python library that builds OAuth and OpenID Connect servers for user authentication and identity management. A vulnerability in OpenID Connect's implicit grant flow allows a registered client to bypass scope restrictions and obtain an ID token with user information it should not have access to. An attacker with a registered application could forge access to user identity data without proper authorization.

Technologies: Authlib, authlib (PyPI). Vendors: Authlib, PyPI.

Quick answers

Is CVE-2026-114619 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-114619 being exploited in the wild.
How severe is CVE-2026-114619?: Medium severity, with a CVSS score of 4.6, published 22 October 2026.
Which products and versions are affected?: Authlib before 1.9.0; authlib (PyPI) < 1.9.0, ECOSYSTEM:introduced=0,fixed=1.9.0.
Is there a fix for CVE-2026-114619?: Yes. authlib (PyPI): upgrade to 1.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114619 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-114619?: Check whether you run Authlib or authlib (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

authlib (PyPI): upgrade to 1.9.0 or later
```
pip install "authlib>=1.9.0"
```

Technical details

OpenIDImplicitGrant.validate_authorization_request() incorrectly validates against the raw client-controlled request.payload.scope instead of the filtered request.scope. This allows a client registered without the openid scope but permitted an ID token response type to add openid to the request, obtain user consent, and receive a signed ID token. The vulnerability requires a registered client and user interaction but permits scope escalation in implicit grant deployments.

Affected products

Authlib Authlib before 1.9.0

Identifiers

CVE-2026-114619
GHSA-q686-2qmg-hqc7
PYSEC-2026-4359

Timeline

2026-10-22: disclosed
2026-10-08: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.