ubuntu-cve-2026-70665
Vulnerability from osv_ubuntu
Doorkeeper OpenID Connect implements an OpenID Connect authentication provider for Rails applications on top of Doorkeeper. Prior to 1.10.4, the Dynamic Client Registration (DCR) endpoint persists client-supplied scopes without validating them against the server's configured scope set. Under certain conditions, this allows a self-registered client to obtain scopes beyond what the server intended to grant. In DynamicClientRegistrationController#application_params, the scopes attribute is assigned directly from params[:scope] with no validation against Doorkeeper.configuration.scopes or optional_scopes. Combined with enforce_configured_scopes being off by default and Doorkeeper's ScopeChecker prioritizing application-level scopes over server-level scopes, this creates a privilege escalation path. This issue is fixed in version 1.10.4.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ruby-doorkeeper-openid-connect",
"binary_version": "1.1.2-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "ruby-doorkeeper-openid-connect",
"purl": "pkg:deb/ubuntu/ruby-doorkeeper-openid-connect@1.1.2-1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.1.2-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ruby-doorkeeper-openid-connect",
"binary_version": "1.6.3-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "ruby-doorkeeper-openid-connect",
"purl": "pkg:deb/ubuntu/ruby-doorkeeper-openid-connect@1.6.3-2?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.5.5-1",
"1.6.3-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ruby-doorkeeper-openid-connect",
"binary_version": "1.8.0-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "ruby-doorkeeper-openid-connect",
"purl": "pkg:deb/ubuntu/ruby-doorkeeper-openid-connect@1.8.0-1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.7.4-2",
"1.8.0-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ruby-doorkeeper-openid-connect",
"binary_version": "1.8.7-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "ruby-doorkeeper-openid-connect",
"purl": "pkg:deb/ubuntu/ruby-doorkeeper-openid-connect@1.8.7-1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.8.7-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "ruby-doorkeeper-openid-connect",
"binary_version": "1.8.11-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "ruby-doorkeeper-openid-connect",
"purl": "pkg:deb/ubuntu/ruby-doorkeeper-openid-connect@1.8.11-1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.8.7-1",
"1.8.11-1"
]
}
],
"aliases": [],
"details": "Doorkeeper OpenID Connect implements an OpenID Connect authentication provider for Rails applications on top of Doorkeeper. Prior to 1.10.4, the Dynamic Client Registration (DCR) endpoint persists client-supplied scopes without validating them against the server\u0027s configured scope set. Under certain conditions, this allows a self-registered client to obtain scopes beyond what the server intended to grant. In DynamicClientRegistrationController#application_params, the scopes attribute is assigned directly from params[:scope] with no validation against Doorkeeper.configuration.scopes or optional_scopes. Combined with enforce_configured_scopes being off by default and Doorkeeper\u0027s ScopeChecker prioritizing application-level scopes over server-level scopes, this creates a privilege escalation path. This issue is fixed in version 1.10.4.",
"id": "UBUNTU-CVE-2026-70665",
"modified": "2026-09-02T16:23:50Z",
"published": "2026-08-25T23:17:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-70665"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-70665"
},
{
"type": "REPORT",
"url": "https://github.com/doorkeeper-gem/doorkeeper-openid_connect/security/advisories/GHSA-8r7r-wh7x-27ff"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-70665"
]
}
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.
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.