Security readout for executives and security teams
Plain-English summary
Keycloak’s CIBA authentication flow can ignore a temporary account lockout. An attacker who already possesses valid client credentials could continue authentication attempts and may obtain tokens while the targeted account should be protected. This weakens an important defense against repeated login attempts but does not, by itself, establish account compromise.
Executive priority
Treat this as a prompt, risk-based remediation rather than an emergency. Prioritize deployments using CIBA for sensitive identities or broadly accessible authentication services. The urgency increases if client credentials may be exposed. Track exact package remediation because product-level version labels alone may produce incorrect conclusions.
Technical view
CVE-2026-9798 is a CWE-305 authentication-bypass condition affecting specified Red Hat build of Keycloak 26.4 and 26.6 packages. During CIBA authentication, temporary brute-force lockout state is not reliably enforced, permitting continued attempts and possible token issuance. Red Hat rates it medium; CVSS 3.1 is 4.3.
Likely exposure
Exposure is most likely where an affected Red Hat Keycloak package is deployed, CIBA is available, and an attacker can use valid client credentials. The supplied records are package- and build-specific; similarly named releases have different affected statuses, so inventory must include exact package identifiers and builds.
Exploitation context
The attacker requires valid client credentials and access to the CIBA flow. The supplied sources do not establish public exploitation, and the CVE is not identified as being in CISA KEV. User interaction is represented in the supplied CVSS vector, but the bundle does not explain its precise form.
Researcher notes
The bundle identifies affected operator and runtime packages across Red Hat Keycloak 26.4 and 26.6, while separately marking 26.4.14 and 26.6.5 unaffected. Because affected build strings appear closely related, validate package-level NEVRA and erratum applicability rather than inferring status from the marketing version. No exploit method or observed campaign is documented.
Mitigation direction
- Match installed Keycloak packages and builds against the Red Hat affected records.
- Apply the applicable Red Hat security erratum for each affected package.
- Review vendor guidance before using any temporary workaround not named in the sources.
- Restrict unnecessary CIBA availability and protect client credentials while remediation is pending.
Validation and detection
- Inventory exact Keycloak versions, package names, build identifiers, and deployment roles.
- Confirm whether CIBA is enabled and reachable in each affected environment.
- Verify installed updates correspond to the applicable Red Hat security erratum.
- Review authentication logs for CIBA activity involving temporarily locked accounts.
- Confirm temporary lockouts prevent CIBA authentication and token issuance after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-305: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-9798 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N2.81.4redhatVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Reported to Red Hat.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineredhat
Made public.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2026:50846CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:50847CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:50848CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:50849CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-9798CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2482470CVE reference, redhat · issue-tracking, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authentication Bypass by Primary Weakness
Authentication Bypass by Primary Weakness represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.