On this page
CVE Details
- Protection status: Protected by Atomicorp rules · About protection statuses
- CVE: CVE-2026-133536
- Name: Org.keycloak:keycloak-services: post-logout redirect uri configuration of a disabled client is still honored, leading to
- Severity: Medium
- CVSS: 4.3 (v3.1) (Medium)
- CVSS version: 3.1
- CVSS source: redhat CNA
- CVSS vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N- Attack vector: Network
- Attack complexity: Low
- Privileges required: None
- User interaction: Required
- Scope: Unchanged
- Confidentiality impact: None
- Integrity impact: Low
- Availability impact: None
- CWE: CWE-601 — URL Redirection to Untrusted Site
- Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-178 (opens in a new tab)
- Vendor: Red Hat
- Vulnerable products: Red Hat Build of Keycloak , Red Hat Single Sign-On 7
- CVE published: 2026-11-20
- CVE last modified: 2026-11-20
- EPSS: 0.0019; 9.1th percentile as of 2026-11-20 (FIRST (opens in a new tab) )
- Latest Update: 2026-11-20
- Selected Rule IDs observed: 340162 , 340163 , 340165 , 344365
- Matching rules: 4; rules with blocking actions: 4
- Would-block Rule IDs: 340162 , 340163 , 340165 , 344365
- Request surfaces inspected: JSON request data, Request URI, Request argument names, Request arguments, Request headers, SOAP request data, XML request data
Technical vulnerability details · CVSS assessments, exploit evidence & CPE data
CVSS assessments
CVSS v3.1 · secalert@redhat.com
- Base score: 4.3
- Base severity: MEDIUM
- Exploitability subscore: 2.8
- Impact subscore: 1.4
- Assessment type: Secondary
- Source identifier: secalert@redhat.com
- Full vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N- Attack vector: Network
- Attack complexity: Low
- Privileges required: None
- User interaction: Required
- Scope: Unchanged
- Confidentiality impact: None
- Integrity impact: Low
- Availability impact: None
- Exploit maturity: Not scored
Exploitability and impact subscores describe the vulnerability’s technical characteristics. Exploit maturity describes the reported state of exploitation; these are separate measures.
Assessment source: NVD record (opens in a new tab) · CVE record (opens in a new tab)
CISA SSVC assessments
These are CISA’s published decision points at the assessment time. They are not a complete organization-specific prioritization decision.
- Provider: CISA ADP
- Provider identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
- SSVC version: 2.0.3
- Role: CISA Coordinator
- Assessment timestamp: 2026-11-20T16:01:49.390504Z
- Exploitation: none
- Automatable: no
- Technical Impact: partial
- Source: CISA ADP in the CVE record (opens in a new tab)
Vulnerable CPE configurations
No vulnerable CPE configurations are supplied in the current NVD record. See the affected-product information and vendor guidance on this page.
Vulnerability Description
A flaw was found in Keycloak. The OpenID Connect (OIDC) logout endpoint continues to honor post-logout redirect rules for disabled clients rather than rejecting the requests. If a disabled client retains permissive redirect configurations, a remote attacker can exploit this issue by supplying an arbitrary redirection target in a logout request, leading to an open redirect that can be used in phishing attacks.
Recommended Actions
Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (340162 , 340163 , 340165 , 344365 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.
Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.
- CNA guidance source: redhat (opens in a new tab)
- Vendor workaround: Administrators can mitigate this flaw by removing permissive redirect configurations from inactive clients or deleting unused clients:
In the Keycloak Admin Console, navigate to the relevant realm and inspect the ‘Clients’ list.
For any client set to disabled, open its settings and clear or restrict the ‘Valid Post Logout Redirect URIs’ and ‘Valid Redirect URIs’ fields, ensuring wildcard characters (’*’) are removed and only explicitly trusted absolute URLs remain.
Alternatively, permanently delete any disabled clients that are obsolete and no longer required.
Caveats: Deleting a client permanently removes its configuration, mappers, service account roles, and credentials. Changes made to client settings in the Admin Console apply immediately to the realm without requiring a Keycloak service restart.
- Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.
Research Notes
Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.
Public Vulnerability References
- NVD (opens in a new tab)
- CVE Record (opens in a new tab)
- CVE authority reference: https://access.redhat.com/security/cve/CVE-2026-133536 (opens in a new tab)
- CVE authority reference: https://bugzilla.redhat.com/show_bug.cgi?id=2577541 (opens in a new tab)
Test or Research Source
- Source: Atomicorp AI Research Framework
- Tags: cve, derived, redirect, waf-probe
Research Note Context
This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.
Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.
Learn More
Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.
Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:
- Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
- Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
- Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
- Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
- Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.
For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .