Loading vulnerability…
CVE-2026-9091 is a logic flaw in Casdoor affecting version 2.362.0 and earlier. In the social-login binding flow, the binding-rule code path in controllers/auth.go invokes HandleLoggedIn directly without first calling checkMfaEnable. As a result, users authenticating through this specific social-login path are granted a logged-in session without enforcement of configured multi-factor authentication requirements. The issue is an authentication-control failure in the login pipeline rather than a memory-safety bug, and it weakens the intended assurance provided by MFA for accounts using the affected flow.
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.
2 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.