CVE-2026-44476

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 6.3Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
59
EG Risk 59/100

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 computed
Severity63% × 45%
Exploitation40% × 40%
Automatability100% × 15%
EPSS PROB
0.6%
EPSS %ILE
45th
KEV
Not listed

Published

June 4, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Aug 25, 2026
Patch available. Sources: github, github_commit.
github_commit Patch Available

commit 561af83dcf (doorkeeper-gem/doorkeeper-openid_connect)

Patch available: doorkeeper-gem/doorkeeper-openid_connect v1.10.0 (contains commit 561af83dcf)

https://github.com/doorkeeper-gem/doorkeeper-openid_connect/commit/561af83dcf
githubMentions a patch (unverified)

Dynamic Client Registration feature creates public clients with client_secret · Advisory · doorkeeper-gem/doorkeeper-openid_connect · GitHub

Affected: 1.10.0

https://github.com/doorkeeper-gem/doorkeeper-openid_connect/security/advisories/GHSA-m6vc-f87m-cc2h

Vendor Advisories for CVE-2026-44476(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-doorkeeper-openid-connect1.10.1-1 ... 1.9.0-1 (9 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-doorkeeper-openid-connect1.10.1-1 ... 1.9.0-1 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-doorkeeper-openid-connect1.8.11-1, 1.8.11-2, 1.8.7-1, 1.9.0-1
  • every version up to 1.10.1-1: fixed in 1.10.1-1
—
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
doorkeeper-openid_connect1.9.0
  • 1.9.0 up to 1.10.0: fixed in 1.10.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 23× 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.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-04 23:22 UTCEPSS rescore
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-03 12:09 UTCOSV refresh
  10. 2026-10-01 19:50 UTCEPSS rescore
  11. 2026-09-30 15:03 UTCEPSS rescore
  12. 2026-09-27 13:48 UTCEPSS rescore
  13. 2026-09-26 15:58 UTCEPSS rescore
  14. 2026-09-20 20:15 UTCEPSS rescore
  15. 2026-09-18 19:28 UTCEPSS rescore
  16. 2026-09-17 19:31 UTCEPSS rescore
  17. 2026-09-16 14:08 UTCEPSS rescore
  18. 2026-09-16 05:15 UTCEPSS rescore
  19. 2026-09-14 05:23 UTCEG score recompute
  20. 2026-09-13 16:47 UTCEPSS rescore
  21. 2026-09-12 15:01 UTCEPSS rescore
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-11 09:37 UTCEPSS rescore
  24. 2026-09-10 09:34 UTCEPSS rescore
  25. 2026-09-09 23:00 UTCEG score recompute
Show 23 more
  1. 2026-09-08 22:00 UTCEPSS rescore
  2. 2026-09-07 16:01 UTCEPSS rescore
  3. 2026-09-06 13:47 UTCEPSS rescore
  4. 2026-09-04 05:06 UTCEPSS rescore
  5. 2026-09-02 14:12 UTCEPSS rescore
  6. 2026-09-01 13:54 UTCEPSS rescore
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 01:22 UTCEPSS rescore
  9. 2026-08-28 21:41 UTCEPSS rescore
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-26 16:22 UTCEG score recompute
  12. 2026-08-26 16:05 UTCEG score recompute
  13. 2026-08-26 14:46 UTCEPSS rescore
  14. 2026-08-25 23:31 UTCEG score recompute
  15. 2026-08-25 22:50 UTCEG score recompute▲ 6.30
  16. 2026-08-25 22:50 UTCMITRE cvelistV5CVSS v3 → 6.3 · CVSS v4 → 6.3
  17. 2026-07-31 05:26 UTCEG score recompute
  18. 2026-07-26 22:16 UTCEG score recompute
  19. 2026-07-23 03:15 UTCEG score recompute
  20. 2026-06-14 23:18 UTCEPSS rescore
  21. 2026-06-13 23:00 UTCEPSS rescore
  22. 2026-06-12 23:12 UTCEPSS rescore
  23. 2026-06-04 15:10 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-44476?
CVE-2026-44476 is a medium vulnerability published on June 4, 2026. 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 clientid, which is public information, can authenticate as that client at the token endpoint and obtain an access token without providing its clientsecret. This occurs…
When was CVE-2026-44476 disclosed?
CVE-2026-44476 was first published on June 4, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44476 actively exploited?
CVE-2026-44476 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44476?
CVE-2026-44476 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-44476?
A fix for CVE-2026-44476 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44476 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44476

Explore →

Is Your Infrastructure Affected by CVE-2026-44476?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.