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.
CVE-2026-70665
This medium-severity CVE scores 4.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.2
- EG Score
- 4.2(medium)
- EG Risk
- 19(Track)EG Risk 19/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity42% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 6%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
September 9, 2026
Advisory Details (2)
Auto-updated Aug 25, 2026commit 24c3cb1729b6 (doorkeeper-gem/doorkeeper-openid_connect)
Patch available: doorkeeper-gem/doorkeeper-openid_connect v1.10.4 (contains commit 24c3cb1729b6)
https://github.com/doorkeeper-gem/doorkeeper-openid_connect/commit/24c3cb1729b69f48649a6f4491dcae69f805000dDCR endpoint persists unvalidated client-supplied scopes · Advisory · doorkeeper-gem/doorkeeper-openid_connect · GitHub
https://github.com/doorkeeper-gem/doorkeeper-openid_connect/security/advisories/GHSA-8r7r-wh7x-27ffAffected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| ruby-doorkeeper-openid-connect | 1.10.1-1 ... 1.9.0-1 (9 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| ruby-doorkeeper-openid-connect | 1.10.1-1 ... 1.9.0-1 (6 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| ruby-doorkeeper-openid-connect | 1.10.1-1, 1.8.11-1, 1.8.11-2, 1.8.7-1, 1.9.0-1 | 1.10.5-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 44× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 11:58 UTCEG score recompute
- 2026-09-19 12:50 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 13:42 UTCEG score recompute
- 2026-09-16 15:09 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 16:01 UTCEG score recompute
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-13 17:45 UTCEG score recompute
- 2026-09-12 18:37 UTCEG score recompute
- 2026-09-12 15:02 UTCEPSS rescore
- 2026-09-11 19:29 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 20:21 UTCEG score recompute
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 06:47 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 07:39 UTCEG score recompute
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-07 08:30 UTCEG score recompute
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 09:18 UTCEG score recompute
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-05 10:11 UTCEG score recompute
Show 19 moreShow fewer
- 2026-09-04 11:02 UTCEG score recompute
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 11:52 UTCEG score recompute
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:28 UTCEG score recompute
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 14:21 UTCEG score recompute
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 15:10 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 16:01 UTCEG score recompute
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 17:32 UTCEG score recompute
- 2026-08-27 17:10 UTCEG score recompute
- 2026-08-26 22:38 UTCEG score recompute
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 23:31 UTCEG score recompute
- 2026-08-25 22:25 UTCEG score recompute
- 2026-08-25 22:24 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-285
Frequently asked(5)
What is CVE-2026-70665?
When was CVE-2026-70665 disclosed?
Is CVE-2026-70665 actively exploited?
What is the CVSS score of CVE-2026-70665?
How do I remediate CVE-2026-70665?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-70665
Is Your Infrastructure Affected by CVE-2026-70665?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.