CVE-2026-44476

MEDIUMPre-NVD 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 0%CVSS: —Exploit: NoneExposed: 0

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

Doorkeeper Openid Connect: Dynamic Client Registration feature creates public clients with client_secret

Impact

The DynamicClientRegistrationController#register action hard-codes confidential: false when creating applications (dynamic_client_registration_controller.rb:18-25), yet the response includes a client_secret and advertises token_endpoint_auth_methods_supported: ["client_secret_basic", "client_secret_post"].

Because Doorkeeper's Application.by_uid_and_secret treats a blank/missing secret as valid for non-confidential (public) clients, an attacker who knows only the client_id (which is public information) can authenticate as the dynamically-registered client at the token endpoint.

Note that Dynamic Client Registration is opt-in feature which is disabled by default so only projects that explicitly enabled it are affected.

Steps to Reproduce

  • Enable dynamic client registration in the initializer
  • POST /oauth/registration with client_name, redirect_uris, and scope
  • Observe: response returns client_secret, but the created
Doorkeeper::Application has confidential: false
  • Call Doorkeeper::Application.by_uid_and_secret(client_id, nil) — it
returns the application (credentials bypass)
  • POST /oauth/token with grant_type=client_credentials and only
client_id (no client_secret) — the token endpoint issues an access token without any secret verification

Patches

Patched in 1.10.0

Workarounds

Upgrade existing applications created with a Dynamic Client registration to have confidential: true

CVSS v3
—
EG Score
0.0(none)
EPSS
18.6%
KEV
Not listed

Published

June 4, 2026

Last Modified

June 4, 2026

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—

Data Freshness Timeline

(refreshed 0× in last 7d / 4× 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-06-14 23:18 UTCEPSS rescore
  2. 2026-06-13 23:00 UTCEPSS rescore
  3. 2026-06-13 08:23 UTCEG score recompute
  4. 2026-06-12 23:12 UTCEPSS rescore
  5. 2026-06-04 15:10 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-44476?
CVE-2026-44476 is a medium vulnerability published on June 4, 2026. Doorkeeper Openid Connect: Dynamic Client Registration feature creates public clients with client_secret Impact The DynamicClientRegistrationController#register action hard-codes confidential: false when creating applications (dynamicclientregistrationcontroller.rb:18-25), yet the response includes…
When was CVE-2026-44476 disclosed?
CVE-2026-44476 was first published in the National Vulnerability Database on June 4, 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 18.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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