CVE-2026-4633

LOWNVD 3.73.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This low-severity CVE scores 3.7 under NVD CVSS v3. EPSS exploit probability: 0.4% (28th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
3.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 3.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in Keycloak. A remote attacker can exploit differential error messages during the identity-first login flow when Organizations are enabled. This vulnerability allows an attacker to determine the existence of users, leading to information disclosure through user enumeration.

CVSS v3
3.7
EG Score
3.7LOWmedium confidence
EG Risk
17
EG Risk 17/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 (value × EchelonGraph’s weight)
Severity37% × 45%
The EG Score, 3.7 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
28th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 23, 2026

Last Modified

June 17, 2026

References (2)

Vendor Advisories for CVE-2026-4633(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)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.keycloak:keycloak-services1.0-alpha-1 ... 9.0.3 (216 versions)
  • 26.5.0 up to 26.6.1: fixed in 26.6.1
  • every version up to 26.4.12: fixed in 26.4.12
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 24× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 94 of 110 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 16 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 19:45 UTCEG score recompute
  2. 2026-10-11 17:00 UTCEG score recompute
  3. 2026-10-11 14:25 UTCEG score recompute
  4. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  7. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  8. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  9. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  10. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  11. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  12. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  13. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  14. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  15. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  16. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  17. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  18. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  19. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  20. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  21. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  22. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  23. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  24. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  25. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 24th percentile
Show 69 more
  1. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  2. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  3. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  4. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  5. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  6. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  7. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  8. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  9. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  10. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  11. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  12. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  13. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  14. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  15. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  16. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  17. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  18. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  19. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  20. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  21. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  22. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  23. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  24. 2026-08-14 19:46 UTCEG score recompute
  25. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  26. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  27. 2026-08-11 23:54 UTCEG score recompute
  28. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  29. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  30. 2026-08-09 06:35 UTCEG score recompute
  31. 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  32. 2026-08-06 01:18 UTCEG score recompute
  33. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  34. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  35. 2026-08-04 10:39 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  36. 2026-08-02 15:56 UTCEG score recompute
  37. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  38. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  39. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  40. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  41. 2026-07-28 15:37 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  42. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  43. 2026-07-25 14:18 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  44. 2026-07-24 14:18 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  45. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  46. 2026-07-23 03:17 UTCEG score recompute
  47. 2026-07-22 14:08 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  48. 2026-07-21 15:25 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  49. 2026-07-20 17:08 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  50. 2026-07-19 14:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  51. 2026-07-19 02:29 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  52. 2026-07-18 10:04 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  53. 2026-07-16 17:03 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  54. 2026-07-15 16:57 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  55. 2026-07-15 02:00 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  56. 2026-07-13 22:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  57. 2026-07-13 06:13 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  58. 2026-07-12 05:46 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  59. 2026-07-11 08:27 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  60. 2026-07-09 19:10 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  61. 2026-07-08 15:16 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  62. 2026-07-06 16:27 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  63. 2026-07-06 02:23 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  64. 2026-07-05 02:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  65. 2026-07-04 06:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  66. 2026-07-01 15:07 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  67. 2026-06-30 23:22 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  68. 2026-06-28 14:07 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  69. 2026-06-28 04:56 UTCEPSS rescoreEPSS 0.3% · 23rd percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-4633?
CVE-2026-4633 is a low-severity vulnerability; its CVE record was published on March 23, 2026. A flaw was found in Keycloak. A remote attacker can exploit differential error messages during the identity-first login flow when Organizations are enabled. This vulnerability allows an attacker to determine the existence of users, leading to information disclosure through user enumeration.
When was CVE-2026-4633 made public?
CVE-2026-4633 was made public on March 23, 2025: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on March 23, 2026. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-4633 actively exploited?
CVE-2026-4633 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-4633?
CVE-2026-4633 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-4633?
A fix for CVE-2026-4633 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-4633 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-4633

Explore →

Is Your Infrastructure Affected by CVE-2026-4633?

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

Book a Demo →Browse All CVEs