Red Hat Security Advisory: Red Hat build of Keycloak 26.2.11 Security Update
Affects Red HatSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 5.4 Medium.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Product Security Red Hat | Affected
| Fixed in– |
AI-suggested
Red Hat recommends applying the security update for Keycloak 26.2.11 available through the Customer Portal. Before updating, users should back up their existing installation, including applications, configuration files, and databases. Since no explicit patch link is provided, users should consult the Red Hat advisory RHSA-2025:22089 for the latest update packages and instructions. No additional mitigation steps are specified by the vendor.
Description
Red Hat has issued a security update for its build of Keycloak version 26.2.11 addressing a moderate severity vulnerability involving deserialization of untrusted data in the LDAP User Federation component (CVE-2025-13467). This vulnerability could potentially allow an attacker to exploit unsafe deserialization processes. The advisory recommends backing up existing installations before applying the update. No explicit patch link is provided in the advisory, and no known exploits are reported in the wild.