CVE-2026-65635

HIGHPre-NVD 8.38.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% 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: cna:eef, epss
Elevated
8.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.3Exploit: Elevated riskExposed: 0

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

Improper Isolation or Compartmentalization vulnerability in malach-it boruta (Elixir.Boruta.Openid module) allows attackers to register OpenID Connect clients with administrative privileges through the dynamic client registration entry point. Boruta.Openid.register_client/3 forwards caller-supplied registration parameters to the administrative client creation path without a public/admin field-level allowlist, so an unauthenticated registrant can set security-sensitive attributes including supported grant types, authorized scopes, PKCE enforcement, public refresh and revocation behavior, token lifetimes, and signing settings. The library does not distinguish between metadata a public registrant is allowed to set and administrative controls that should require operator approval.

This vulnerability is associated with program files lib/boruta/openid.ex and program routines 'Elixir.Boruta.Openid':register_client/3, 'Elixir.Boruta.Openid':parse_registration_params/2.

This issue affects boruta from 2.3.0 before 2.3.7.

CVSS v3
8.3
EG Score
8.3(medium)
EG Risk
53(Track)
EG Risk 53/100SSVC: Track

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
Severity83% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

July 30, 2026

Last Modified

July 31, 2026

Advisory Details (5)

Auto-updated Jul 30, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit 95619a1beaff (malach-it/boruta_auth)

Fix landed in malach-it/boruta_auth commit 95619a1beaff — awaiting tagged release

https://github.com/malach-it/boruta_auth/commit/95619a1beaff68fa766cca9b388e7c780d182525
github_commit

commit 82584c854a33 (malach-it/boruta_auth)

Fix landed in malach-it/boruta_auth commit 82584c854a33 — awaiting tagged release

https://github.com/malach-it/boruta_auth/commit/82584c854a332482232fd25301ab12a835f9f643
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-65635
generic

Boruta dynamic client registration allows creation of over-privileged OAuth clients | Erlang Ecosystem Foundation CNA

https://cna.erlef.org/cves/CVE-2026-65635.html
github Patch Available🟡 PoC Available

Dynamic registration can create over-privileged clients · Advisory · malach-it/boruta_auth · GitHub

https://github.com/malach-it/boruta_auth/security/advisories/GHSA-w869-fcf2-68vp

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
boruta2.3.0 ... 2.3.6 (7 versions)2.3.7—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 55× 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 00:34 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-25 01:14 UTCEG score recompute
  4. 2026-08-24 13:50 UTCEG score recompute
  5. 2026-08-23 03:26 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 04:36 UTCEG score recompute
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 05:45 UTCEG score recompute
  10. 2026-08-20 22:56 UTCEPSS rescore
  11. 2026-08-19 19:30 UTCEG score recompute
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-18 19:12 UTCEG score recompute
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 20:13 UTCEG score recompute
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-16 21:13 UTCEG score recompute
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 09:48 UTCEG score recompute
  20. 2026-08-15 10:59 UTCEG score recompute
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 00:45 UTCEG score recompute
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-12 14:31 UTCEG score recompute
  25. 2026-08-12 13:51 UTCEPSS rescore
Show 30 more
  1. 2026-08-11 15:41 UTCEG score recompute
  2. 2026-08-11 04:17 UTCEG score recompute
  3. 2026-08-11 00:00 UTCEPSS rescore
  4. 2026-08-09 18:02 UTCEG score recompute
  5. 2026-08-09 13:47 UTCEPSS rescore
  6. 2026-08-08 19:13 UTCEG score recompute
  7. 2026-08-08 16:37 UTCEPSS rescore
  8. 2026-08-07 20:24 UTCEG score recompute
  9. 2026-08-06 21:35 UTCEG score recompute
  10. 2026-08-06 13:47 UTCEPSS rescore
  11. 2026-08-05 22:44 UTCEG score recompute
  12. 2026-08-05 19:17 UTCEPSS rescore
  13. 2026-08-05 19:17 UTCEPSS rescore
  14. 2026-08-04 23:54 UTCEG score recompute
  15. 2026-08-04 15:10 UTCEPSS rescore
  16. 2026-08-04 12:27 UTCEG score recompute
  17. 2026-08-04 10:39 UTCEPSS rescore
  18. 2026-08-03 12:50 UTCEG score recompute
  19. 2026-08-03 10:36 UTCEPSS rescore
  20. 2026-08-02 02:33 UTCEG score recompute
  21. 2026-08-02 02:27 UTCEPSS rescore
  22. 2026-08-01 15:08 UTCEG score recompute
  23. 2026-08-01 04:16 UTCEPSS rescore
  24. 2026-07-31 16:18 UTCEG score recompute
  25. 2026-07-30 17:26 UTCEG score recompute
  26. 2026-07-30 17:04 UTCEG score recompute
  27. 2026-07-30 16:52 UTCEG score recompute
  28. 2026-07-30 15:31 UTCEG score recompute
  29. 2026-07-30 14:56 UTCEG score recompute
  30. 2026-07-30 14:56 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-65635?
CVE-2026-65635 is a high vulnerability published on July 30, 2026. Improper Isolation or Compartmentalization vulnerability in malach-it boruta (Elixir.Boruta.Openid module) allows attackers to register OpenID Connect clients with administrative privileges through the dynamic client registration entry point. Boruta.Openid.register_client/3 forwards caller-supplied…
When was CVE-2026-65635 disclosed?
CVE-2026-65635 was first published in the National Vulnerability Database on July 30, 2026, with the most recent update on July 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65635 actively exploited?
CVE-2026-65635 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 77.9% of all scored CVEs.
What is the CVSS score of CVE-2026-65635?
CVE-2026-65635 has a CVSS v4.0 base score of 8.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-65635?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65635, 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-65635

Explore →

Is Your Infrastructure Affected by CVE-2026-65635?

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

Start Free Scan →Browse All CVEs