Loading vulnerability…
CVE-2025-14777 is an insecure direct object reference and broken access control vulnerability in Keycloak's admin API endpoints for authorization resource management. The flaw affects authorization resource operations in ResourceSetService and PermissionTicketService. Authorization is evaluated against the resourceServer, or client, identifier supplied in the API request, but the backend lookup and modification paths use only the resource identifier for findById and delete operations. This authorization-to-object mismatch allows a user who is legitimately granted fine-grained administrative permissions over one client in a realm to act on resources owned by a different client in the same realm by providing a valid target resource ID. As a result, cross-client update or deletion of authorization resources can occur despite the attacker lacking administrative rights over the victim client.
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.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.