Skip to content
Fencer Intel
medium 5.9

CVE-2026-9793 json

Keycloak: keycloak: security policy bypass in jwe-encrypted request object processing

published 5mo ago modified 16d ago also GHSA-p3v8-fm5p-v84h , EUVD-2026-32707

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 5%
public exploits
0
none known

Summary

A flaw was found in Keycloak. When a JSON Web Encryption (JWE) encrypted request object is submitted, Keycloak may incorrectly process unsigned claims if the decrypted content is raw JSON, bypassing the configured signature policy. This allows a remote attacker to submit unauthorized claims, leading to a compromise of data integrity within the OpenID Connect (OIDC) authorization flow. While a redirect URI allowlist acts as a compensating control, this vulnerability violates OIDC Core and Financial-grade API (FAPI) signing requirements.

Patch / fix

  • Red Hat Red Hat build of Keycloak 26.4 26.4-22, 26.4.14-1
  • Red Hat Red Hat build of Keycloak 26.6 26.6-11, 26.6.5-1

Is CVE-2026-9793 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-9793 updated cvss 5.9

keycloak: Keycloak: Security policy bypass in JWE-encrypted request object processing

  • Red Hat build of Keycloak 26.4 rhbk/keycloak-rhel9 26.4-22, rhbk/keycloak-rhel9-operator 26.4-22, rhbk/keycloak-operator-bundle 26.4.14-1
    fixed: vendor fix RHSA-2026:50847
  • Red Hat build of Keycloak 26.4.14
    fixed: vendor fix RHSA-2026:50846
  • Red Hat build of Keycloak 26.6 rhbk/keycloak-rhel9 26.6-11, rhbk/keycloak-rhel9-operator 26.6-11, rhbk/keycloak-operator-bundle 26.6.5-1
    fixed: vendor fix RHSA-2026:50849
  • Red Hat build of Keycloak 26.6.5
    fixed: vendor fix RHSA-2026:50848

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
5mo ago

Exploit prediction

0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
GitHub 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.keycloak:keycloak-services
<=26.6.4
 no fix listed

Affected products

  • Red Hat Red Hat build of Keycloak 26.4
  • Red Hat Red Hat build of Keycloak 26.4.14
  • Red Hat Red Hat build of Keycloak 26.6
  • Red Hat Red Hat build of Keycloak 26.6.5

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.