CVE-2026-9098 affects Casdoor 2.362.0 and earlier. The SAML Assertion Consumer Service callback handler at /api/acs in controllers/auth.go accepts any well-formed SAMLResponse without verifying that the response is tied to an AuthnRequest previously initiated by Casdoor. The handler therefore fails to enforce request-response correlation for SAML authentication flows. In addition, if an administrator disables or deletes an upstream Identity Provider after a SAML flow has begun, Casdoor still processes the response using the provider snapshot loaded at the start of the request. These flaws allow unsolicited SAML responses from a registered upstream IdP, as well as replay of a legitimately captured SAML response in a different session or after the original authentication flow has ended, to be accepted and converted into a valid Casdoor session.
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.
1 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.