UBUNTU-CVE-2026-114619 (CVE-2026-114619)
Vulnerability from osv_ubuntu – Published: 2026-10-22 22:18 – Updated: 2026-10-28 17:50 – Source websiteAuthlib 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.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-authlib",
"binary_version": "0.15.5-1ubuntu0.1~esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:22.04:LTS",
"name": "python-authlib",
"purl": "pkg:deb/ubuntu/python-authlib@0.15.5-1ubuntu0.1~esm2?arch=source\u0026distro=esm-apps/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.15.4-1",
"0.15.5-1",
"0.15.5-1ubuntu0.1~esm1",
"0.15.5-1ubuntu0.1~esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-authlib",
"binary_version": "1.3.0-1ubuntu0.1~esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:24.04:LTS",
"name": "python-authlib",
"purl": "pkg:deb/ubuntu/python-authlib@1.3.0-1ubuntu0.1~esm2?arch=source\u0026distro=esm-apps/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.2.1-1",
"1.3.0-1",
"1.3.0-1ubuntu0.1~esm1",
"1.3.0-1ubuntu0.1~esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-authlib",
"binary_version": "1.7.2-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "python-authlib",
"purl": "pkg:deb/ubuntu/python-authlib@1.7.2-2?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.6.7-1",
"1.7.2-1",
"1.7.2-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "python3-authlib",
"binary_version": "1.6.7-1ubuntu0.1~esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:26.04:LTS",
"name": "python-authlib",
"purl": "pkg:deb/ubuntu/python-authlib@1.6.7-1ubuntu0.1~esm1?arch=source\u0026distro=esm-apps/resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.6.0-1",
"1.6.5-1",
"1.6.6-1",
"1.6.7-1",
"1.6.7-1ubuntu0.1~esm1"
]
}
],
"aliases": [],
"details": "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\u0027s 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.",
"id": "UBUNTU-CVE-2026-114619",
"modified": "2026-10-28T17:50:37Z",
"published": "2026-10-22T22:18:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-114619"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-114619"
},
{
"type": "REPORT",
"url": "https://github.com/authlib/authlib/commit/e3bd41cb29dcfee434453b135ffb487884baeedf"
},
{
"type": "REPORT",
"url": "https://github.com/authlib/authlib/pull/945"
},
{
"type": "REPORT",
"url": "https://github.com/authlib/authlib/releases/tag/v1.9.0"
},
{
"type": "REPORT",
"url": "https://github.com/authlib/authlib/security/advisories/GHSA-q686-2qmg-hqc7"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-114619"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.