Quick answers
- Is CVE-2026-9096 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-9096 being exploited in the wild.
- How severe is CVE-2026-9096?
- High severity, with a CVSS score of 7.5, published 28 May 2026.
- Which products and versions are affected?
- github.com/casdoor/casdoor (Go) <= 1.1000.1-0.20260321120606-239e8bd69487, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.1000.1-0.20260321120606-239e8bd69487.
- Is there a fix for CVE-2026-9096?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-9096 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-9096?
- Check whether you run github.com/casdoor/casdoor (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Casdoor versions 2.362.0 and earlier contain a vulnerability where SAML assertion time bounds (NotOnOrAfter and NotBefore) are not enforced. While the underlying 'gosaml2' library performs these checks and populates the 'assertionInfo.WarningInfo' field with the results, the 'ParseSamlResponse()' function in Casdoor's 'object/saml_sp.go' fails to inspect this field. Consequently, expired or premature assertions are accepted as valid, allowing for session issuance regardless of the assertion's intended validity period. This is a network-reachable vulnerability requiring no prior authentication or user interaction. As of the advisory date, no patch is available.
Affected products
- Casdoor Casdoor <= 2.362.0
Identifiers
- CVE-2026-9096
- GHSA-rgq2-93gj-ffxg
- GO-2026-5899
Timeline
- 2026-05-28: disclosed
- 2026-05-28: advisory