CVE-2026-18963

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-18. a secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3%CVSS: 9.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

A flaw was found in the reset-credentials flow of the keycloak-services component, which is the core engine for identity and access management in Red Hat Build of Keycloak. The issue allows an unauthenticated attacker to force the password reset process for any user without needing to click the required email verification link. This can result in the attacker gaining full control over target user accounts by directly setting new credentials.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
72(Track)
EG Risk 72/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
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
3%
EPSS %ILE
87%
KEV
Not listed

Published

August 18, 2026

Last Modified

September 8, 2026

Advisory Details (7)

Auto-updated Sep 15, 2026
Patch available. Sources: redhat.
generic

SSA-503852

https://cert-portal.siemens.com/productcert/html/ssa-503852.html
redhat

2511595 – (CVE-2026-18963) CVE-2026-18963 keycloak-services: keycloak-services: Unauthenticated account takeover via reset-credentials flow bypass

https://bugzilla.redhat.com/show_bug.cgi?id=2511595
redhat Patch Available

CVE-2026-18963 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-18963
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:56524
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:56523
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:56520
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:56519

Vendor Advisories for CVE-2026-18963(5)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhbk/keycloak-rhel9-operator:26.6-122026-08-18redhat
redhatrhbk-openshift-rhel9/rhbk-openshift-rhel92026-08-18redhat
redhatrhbk/keycloak-rhel9-operator:26.4-232026-08-18redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.keycloak:keycloak-services26.7.0, 26.7.126.7.2—

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 303 total refreshes for this CVE.

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

Publicly available exploits

(10 references)

Working exploit code is in the public domain (9 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCynsmroztas/KeySniper
    First seen Sep 6, 2026

    **CVE-2026-18963** — unauthenticated Keycloak account takeover via the reset-credentials flow.

    Open source ↗
  • GitHub PoC0xlyvio/CVE-2026-18963-keycloak
    First seen Sep 5, 2026

    CVE-2026-18963 — Keycloak reset-credentials bypass -> Account Takeover

    Open source ↗
  • GitHub PoCEQSTLab/CVE-2026-18963
    First seen Sep 1, 2026

    Kecloak reset-credentials flow bypass

    Open source ↗
  • GitHub PoCalt3kx/CVE-2026-18963
    First seen Aug 27, 2026

    CVE-2026-18963 Keycloak Reset-Credentials State Bypass Detector

    Open source ↗
  • GitHub PoCprot0tw/Keycloak_CVE-2026-18963_PoC
    First seen Aug 25, 2026

    This repo is poc of cve-2026-18963. Please use it on legal products (lab, local,...).

    Open source ↗
  • GitHub PoCT0w0T/POC-CVE-2026-18963
    First seen Aug 24, 2026
    Open source ↗
  • GitHub PoCRed-Darkin/CVE-2026-18963-keycloak
    First seen Aug 24, 2026
    Open source ↗
  • GitHub PoCkyos-public/keycloak-cve-2026-18963-hunt
    First seen Aug 20, 2026

    Hunt for CVE-2026-18963 exploitation traces (Keycloak unauthenticated account takeover) in the Keycloak database

    Open source ↗
  • GitHub PoCSnizi/CVE-2026-18963-Exploit
    First seen Aug 20, 2026

    Exploit for KeyCloak CVE-2026-18963

    Open source ↗
  • Nucleihttp/cves/2026/CVE-2026-18963.yaml
    First seen Jan 1, 2026

    Keycloak < 26.7.2 - Unauthenticated Account Takeover via Reset-Credentials Bypass

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-18963?
CVE-2026-18963 is a critical vulnerability published on August 18, 2026. A flaw was found in the reset-credentials flow of the keycloak-services component, which is the core engine for identity and access management in Red Hat Build of Keycloak. The issue allows an unauthenticated attacker to force the password reset process for any user without needing to click the…
When was CVE-2026-18963 disclosed?
CVE-2026-18963 was first published in the National Vulnerability Database on August 18, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18963 actively exploited?
CVE-2026-18963 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3% probability of exploitation in the next 30 days, which ranks it in the top 12.5% of all scored CVEs.
What is the CVSS score of CVE-2026-18963?
CVE-2026-18963 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-18963?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18963, 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-18963

Explore →

Is Your Infrastructure Affected by CVE-2026-18963?

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

Start Free Scan →Browse All CVEs