Loading vulnerability…
CVE-2026-18573 is a policy enforcement flaw in the keycloak-services component of Keycloak. The vulnerability arises during client update operations when a realm administrator has configured client policies intended to enforce stronger authentication requirements on confidential clients. Due to improper evaluation of client state during the update path, a user with client management permissions can create a client as public and subsequently update it to a confidential client while retaining weaker authentication characteristics that should have been rejected by policy. As a result, Keycloak can persist confidential clients that do not comply with the realm’s intended authentication hardening requirements.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
7 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.