CVE-2026-96453

Org.keycloak/keycloak-admin-cli: keycloak-admin-cli: kcadm custom truststore accepts arbitrary self-signed certificates

  • High 8.0

Description

A flaw was found in the Keycloak Admin CLI kcadm tool, which is used by administrators to manage Keycloak servers from the command line. When a custom truststore is provided to verify the server identity, the tool incorrectly accepts any self-signed certificate as long as the hostname matches. This allows a network attacker to impersonate the Keycloak server, steal administrative credentials, and perform unauthorized management actions.

Key facts

Published
5 Nov 2026
Last changed
9 Nov 2026
Assigned by
redhat
EPSS
0.22% likely to be exploited in the next 30 days, higher than 12.651% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 8.0CVSS 3.1, Highfrom the CNA (redhat)CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N

What to do

  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. --- CME Mitigation Guidance (2026-11-06) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to disable TrustSelfSignedStrategy in the Keycloak Admin CLI HTTP client configuration and enforce validation strictly against the configured custom truststore: upgrade to Red Hat build of Keycloak 26.4.17 / 26.6.8 (or the corresponding fixed Red Hat builds), which disable TrustSelfSignedStrategy in the HTTP client and enforce certificate verification against the provided truststore, closing all 2 injection vectors (Man-in-the-Middle network interception, DNS redirection). Until patched, this is a concern on Administrators executing kcadm with a custom truststore option, so Avoid executing kcadm with custom truststores across untrusted networks, and restrict network paths and DNS resolution between client hosts and Keycloak endpoints. As a compensating measure, Cryptographically verify DNS response authenticity using DNSSEC validation to CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

CNA context is abbreviated; consult the original record for the complete statements.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat build of Keycloak 26.4
  • Default status: affected
  • 26.4.17-2 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.4
  • Default status: affected
  • 26.4-29 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.4
  • Default status: affected
  • 26.4-30 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.4.17
  • Default status: unaffected
Red HatRed Hat build of Keycloak 26.4.17
  • Default status: unaffected
Red HatRed Hat build of Keycloak 26.4.17
  • Default status: unaffected
Red HatRed Hat build of Keycloak 26.6
  • Default status: affected
  • 26.6.8-2 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.6
  • Default status: affected
  • 26.6-24 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.6
  • Default status: affected
  • 26.6-24 up to but excluding * (unaffected)
Red HatRed Hat build of Keycloak 26.6.8
  • Default status: unaffected
Red HatRed Hat build of Keycloak 26.6.8
  • Default status: unaffected
Red HatRed Hat build of Keycloak 26.6.8
  • Default status: unaffected
Red HatRed Hat AMQ Broker 7
  • Default status: unaffected
Red HatRed Hat Fuse 7
  • Default status: unaffected
Red HatRed Hat JBoss Enterprise Application Platform 7
  • Default status: unaffected
Red HatRed Hat JBoss Enterprise Application Platform 7
  • Default status: unaffected
Red HatRed Hat JBoss Enterprise Application Platform 7
  • Default status: unaffected
Red HatRed Hat JBoss Enterprise Application Platform 8
  • Default status: unaffected
Red HatRed Hat JBoss Enterprise Application Platform Expansion Pack
  • Default status: unaffected
Red HatRed Hat Satellite 6
  • Default status: unaffected
Red HatRed Hat Single Sign-On 7
  • Default status: affected
Red HatRed Hat Single Sign-On 7
  • Default status: unaffected
Red HatRed Hat Single Sign-On 7
  • Default status: affected

Timeline

  1. 22 Sep 2026 Reported to Red Hat.
  2. 5 Nov 2026 Made public.
  3. 5 Nov 2026 Published

Weakness

References