Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-18963 – Unauthenticated Account Takeover (Password Reset Bypass) – Red Hat Build of Keycloa

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-18963 is a critical weak-password-recovery vulnerability (CWE-640) in the reset-credentials (forgot password) flow of Red Hat Build of Keycloak. Due to improper state validation in that flow, an unauthenticated remote attacker can bypass the email verification step and force a password reset on any user account, leading to full account takeover. Red Hat rates it Critical with a CVSS v3.1 base score of 9.1.

Technical details

  • Root cause: Improper state validation within the reset-credentials (forgot-password) authentication flow, classified as CWE-640 (Weak Password Recovery Mechanism for Forgotten Password).
  • Trigger conditions: An attacker interacts with the exposed reset-credentials flow without needing valid credentials or user interaction from the victim.
  • Attack vector: Network-based, low attack complexity, no privileges required, no user interaction required.
  • Impact: Bypass of email verification during password reset, allowing an unauthenticated attacker to force a credential reset and gain full control of any user account (high confidentiality and integrity impact; no direct availability impact per the CVSS vector).

Affected software

  • Red Hat Build of Keycloak (keycloak-services component)
  • rhbk-keycloak-rhel9
  • rhbk-openshift-rhel9
  • Red Hat JBoss Enterprise Application Platform Expansion Pack
  • Not affected: Red Hat Single Sign-On 7

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: At the time of publication, Red Hat states that no patched version or mitigation meeting its security criteria is yet available. Security teams should monitor Red Hat and Keycloak advisories closely and apply the fixed build as soon as one is released.
  • If no patch is available: Since no vetted workaround currently exists, restrict or closely monitor access to the reset-credentials/forgot-password endpoint (e.g., via WAF rules, rate limiting, or temporarily disabling self-service password reset) until an official fix ships, and monitor authentication logs for anomalous password-reset activity on user accounts.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: form action containing /auth/realms/, an href of /keycloak/img/favicon.ico, an href containing /keycloak/
  • URL of a loaded script: keycloak.js, keycloak-js-<version>.min.js
  • JavaScript object present once the page runs: Keycloak

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge