Loading vulnerability…
CVE-2026-7504 is an open redirect vulnerability in Keycloak caused by a mismatch between Keycloak's redirect URI validation logic and Java URI parsing behavior during redirect handling. The flaw occurs when a malicious redirect URI includes multiple @ characters in the user-info portion of the authority component. In this condition, Java's URI implementation does not expose the user-info to Keycloak as expected and leaves only the raw authority available. As a result, Keycloak's validation logic fails to recognize the malformed user-info and falls back to wildcard-based comparison against configured valid redirect URIs. If a client is configured with a wildcard entry in the Valid Redirect URIs setting, the crafted redirect can be incorrectly accepted, allowing redirection to an unauthorized destination. The issue affects redirect-based authentication flows and is particularly relevant to OAuth/OIDC scenarios where post-authentication redirects may carry sensitive artifacts.
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.