{"answers":{"affected":"2 open source packages ship an affected version, including doorkeeper-openid_connect.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44476 exists.","fix":"Upgrade doorkeeper-openid_connect to 1.10.0 or later.","what":"CVE-2026-44476 is a medium-severity authentication bypass vulnerability in doorkeeper-gem doorkeeper-openid_connect, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-44476 and fix it if it is affected.\n\nWhat it is: CVE-2026-44476 is a medium-severity authentication bypass vulnerability in doorkeeper-gem doorkeeper-openid_connect, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44476 exists.\n\nAffected packages and fixed versions:\n- doorkeeper-openid_connect (RubyGems): affected from 1.9.0; fixed in 1.10.0\n- doorkeeper-openid_connect (RubyGems): affected from 1.9.0; fixed in 1.10.0\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-44476/ (Markdown: https://insights.sbomify.com/CVE-2026-44476/index.md)","id":"CVE-2026-44476","markdown":"https://insights.sbomify.com/CVE-2026-44476/index.md","name":"CVE-2026-44476","record":{"aliases":["DEBIAN-CVE-2026-44476","GHSA-m6vc-f87m-cc2h","UBUNTU-CVE-2026-44476"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Ruby OAuth library","requires_auth":"none","summary":"Attackers can authenticate as dynamically registered clients without a secret, bypassing authentication in Doorkeeper OpenID Connect when this feature is enabled.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"},{"id":"CWE-1390","name":"Weak Authentication"}],"description":"Doorkeeper is an OAuth 2 provider for Ruby on Rails. In version 1.9.0, an attacker who knows only a dynamically registered client's client_id, which is public information, can authenticate as that client at the token endpoint and obtain an access token without providing its client_secret. This occurs because the Dynamic Client Registration feature creates applications with confidential: false hard-coded, even though the registration response returns a client_secret and advertises support for the client_secret_basic and client_secret_post authentication methods; since Doorkeeper treats a blank or missing secret as valid for non-confidential (public) clients, the secret is never verified. Only projects that have explicitly enabled Dynamic Client Registration, which is disabled by default, are affected. This issue is fixed in version 1.10.0.","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Doorkeeper OpenID Connect: Dynamic Client Registration feature creates public clients with client_secret","id":"CVE-2026-44476","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"CloudNativePG: Metrics exporter allows privilege escalation to PostgreSQL superuser and OS RCE","id":"CVE-2026-44477"},"packages":[{"ecosystem":"RubyGems","fixed":["1.10.0"],"introduced":["1.9.0"],"last_affected":[],"package":"doorkeeper-openid_connect","purl":null,"source":"GHSA-m6vc-f87m-cc2h"},{"ecosystem":"RubyGems","fixed":["1.10.0"],"introduced":["1.9.0"],"last_affected":[],"package":"doorkeeper-openid_connect","purl":"pkg:gem/doorkeeper-openid_connect","source":"GHSA-m6vc-f87m-cc2h"}],"prev":{"headline":"Ella Core: UE Security Capability bypass on NGAP PathSwitchRequest","id":"CVE-2026-44475"},"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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-26","vendors":["doorkeeper-gem"]},"summary":"Attackers can authenticate as dynamically registered clients without a secret, bypassing authentication in Doorkeeper OpenID Connect when this feature is enabled.","url":"https://insights.sbomify.com/CVE-2026-44476/"}