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
Trending — 3 sources updated this weekElevated
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.3(medium)
EG Risk
59(Attend)
EG Risk 59/100SSVC: Attend

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%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

June 4, 2026

Last Modified

August 26, 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
github Patch Available

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

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFixed inDependents
doorkeeper-openid_connect1.9.01.10.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 7× 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-08-26 16:22 UTCEG score recompute
  2. 2026-08-26 16:05 UTCEG score recompute
  3. 2026-08-26 14:46 UTCEPSS rescore
  4. 2026-08-25 23:31 UTCEG score recompute
  5. 2026-08-25 22:50 UTCEG score recompute▲ 6.30
  6. 2026-08-25 22:50 UTCMITRE cvelistV5CVSS v3 → 6.3 · CVSS v4 → 6.3
  7. 2026-07-31 05:26 UTCEG score recompute
  8. 2026-07-26 22:16 UTCEG score recompute
  9. 2026-07-23 03:15 UTCEG score recompute
  10. 2026-06-14 23:18 UTCEPSS rescore
  11. 2026-06-13 23:00 UTCEPSS rescore
  12. 2026-06-12 23:12 UTCEPSS rescore
  13. 2026-06-04 15:10 UTCEG score recompute

Related CVEs(same CWE)

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 in the National Vulnerability Database on June 4, 2026, with the most recent update on August 26, 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% probability of exploitation in the next 30 days, which ranks it in the top 75.4% of all scored CVEs.
What is the CVSS score of CVE-2026-44476?
CVE-2026-44476 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-44476?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44476, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs