Analyst readout for executives and security teams
Plain-English summary
Keycloak may trust unsigned information inside an encrypted OIDC request when that decrypted content is raw JSON. An attacker could tamper with authorization-flow claims even when policy requires signatures. The issue is medium severity because exploitation is remote but rated high complexity, with integrity impact rather than confidentiality or availability impact.
Executive priority
Prioritize assessment for identity systems supporting regulated, financial-grade, or high-integrity authorization flows. Treat patching as important once Red Hat publishes concrete update guidance, while immediately validating redirect URI allowlists and affected client configurations.
Technical view
CVE-2026-9793 is a CWE-347 signature-verification flaw in Red Hat Build of Keycloak. JWE-encrypted request object handling may process unsigned claims from raw JSON after decryption, bypassing configured request-object signature policy and violating OIDC Core and FAPI signing requirements.
Likely exposure
Exposure is most likely in Red Hat Build of Keycloak deployments, including rhbk/keycloak-rhel9, using OIDC flows with JWE-encrypted request objects and signature policy requirements. The source bundle does not provide affected version ranges.
Exploitation context
Sources rate this as network-accessible, unauthenticated, no user interaction, and high attack complexity. KEV status is false, and the provided sources do not report active exploitation. A strict redirect URI allowlist is described as a compensating control.
Researcher notes
The key uncertainty is version scope and remediation status; the bundle lists default affected status but no version range or fixed release. Analysis should focus on JWE request-object processing, unsigned claim acceptance after decryption, and policy enforcement consistency with OIDC Core and FAPI.
Mitigation direction
- Check Red Hat CVE and Bugzilla guidance for fixed builds or package updates.
- Apply vendor-provided Keycloak updates when available for your affected deployment.
- Verify redirect URI allowlists are strict, current, and limited to trusted destinations.
- Review OIDC/FAPI clients that rely on signed request-object enforcement.
- Avoid configuration changes that weaken request-object signature requirements.
Validation and detection
- Inventory Red Hat Build of Keycloak and rhbk/keycloak-rhel9 deployments.
- Identify clients accepting JWE-encrypted OIDC request objects.
- Confirm signature policy expectations for OIDC Core and FAPI clients.
- Review redirect URI allowlists for broad or stale entries.
- Monitor authorization logs for unexpected claims in encrypted request-object flows.
Public sources used
Based on public source material and reviewed before publication.
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-347: 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 lookupCVE-2026-9793 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
- 5.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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:H/PR:N/UI:N/S:U/C:N/I:H/A:N 2.2 3.6 redhat Vulnerability scoring details
Base CVSS 3.1 score
5.9 MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timeline redhat
Reported to Red Hat.
- CVE reserved CVE Program
The CVE ID was reserved by the assigning CNA.
- Source timeline redhat
Made public.
- CVE published CVE Program
The CVE record was published.
- CVE updated CVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 source CVE List V5
- https://access.redhat.com/security/cve/CVE-2026-9793 CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2482460 CVE 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.
Improper Verification of Cryptographic Signature
Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.