Loading vulnerability…
CVE-2026-7500 is an improper access control vulnerability in Keycloak affecting the Account REST API disablement logic. When Keycloak is started with the feature flags --features-disabled=account,account-api, the Account REST API is expected to be disabled. However, the disablement is incomplete: five endpoints under the versioned /account/v1alpha1 path remain accessible and fully functional, including both read and write operations. The flaw exists because those endpoints do not invoke the checkAccountApiEnabled() gate that correctly blocks other endpoints in the same REST service class. As a result, the feature-disabled state is inconsistently enforced, allowing continued access to functionality that administrators intended to turn off.
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.
--features-disabled=account,account-api to block all Account REST API functionality on affected versions. Until the fix is applied, restrict access to the affected versioned Account API endpoints using compensating controls such as reverse-proxy filtering, application gateway policy, network segmentation, or other access-control enforcement that explicitly denies requests to the residual Account API paths. Review whether users retain permissions to use the API and reduce those permissions where possible.Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 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.