{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-70665 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-70665 is a medium-severity vulnerability in doorkeeper-gem doorkeeper-openid_connect, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-70665 and fix it if it is affected.\n\nWhat it is: CVE-2026-70665 is a medium-severity vulnerability in doorkeeper-gem doorkeeper-openid_connect, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-70665 in the wild and no public exploit code.\n\nAffected product: doorkeeper-gem doorkeeper-openid_connect. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-70665/ (Markdown: https://insights.sbomify.com/CVE-2026-70665/index.md)","id":"CVE-2026-70665","markdown":"https://insights.sbomify.com/CVE-2026-70665/index.md","name":"CVE-2026-70665","record":{"aliases":["DEBIAN-CVE-2026-70665","GHSA-8r7r-wh7x-27ff","UBUNTU-CVE-2026-70665"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"Rails OpenID Connect library","requires_auth":"none","summary":"Attackers can register clients with unauthorized scopes to gain elevated access in Rails applications using Doorkeeper OpenID Connect.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Doorkeeper OpenID Connect: DCR endpoint persists unvalidated client-supplied scopes","id":"CVE-2026-70665","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Lemur: Server-Side Request Forgery via the ACME client following server-controlled URLs","id":"CVE-2026-70666"},"packages":[],"prev":{"headline":"pay-rails/pay: non-constant-time HMAC comparison in Paddle Billing webhook signature verifier","id":"CVE-2026-70658"},"products":["doorkeeper-openid_connect"],"published":"2026-08-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-27","vendors":["doorkeeper-gem"]},"summary":"Attackers can register clients with unauthorized scopes to gain elevated access in Rails applications using Doorkeeper OpenID Connect.","url":"https://insights.sbomify.com/CVE-2026-70665/"}