ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-9096

Casdoor versions 2.362.0 and earlier do not enforce SAML assertion time bounds.

Published May 28, 2026 · catalog updated Jun 17, 2026 · Casdoor versions 2.362.0 and

Check if you run it

No confirmed exploitation is on record for CVE-2026-9096. EPSS is 0.43%. Act only if a listed version of Casdoor versions 2.362.0 and is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Casdoor versions 2.362.0 and).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.43%
Remediation
Version ranges on file
Affected products
stated named in the record

Casdoor versions 2.362.0 and earlier do not enforce SAML assertion time bounds. The gosaml2 library reports all time-validation results, including NotOnOrAfter and NotBefore, in the assertionInfo.WarningInfo field. However, ParseSamlResponse() never reads this field, meaning that time bounds are computed by the library but silently discarded before the user session is issued.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • stated named in the record<= 2.362.0

How to fix CVE-2026-9096

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-9096. EPSS is 0.43%. Act only if a listed version of Casdoor versions 2.362.0 and is installed.

Which versions are affected?

Compare what you have installed with named in the record <= 2.362.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.43%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. May 28, 2026 · NIST NVD

    Detected

    Casdoor versions 2.362.0 and earlier do not enforce SAML assertion time bounds. The gosaml2 library reports all time-validation results, including NotOnOrAfter and NotBefore, in the assertionInfo.WarningInfo field. However, ParseSamlResponse() never reads this field, meaning that time bounds are computed by the library but silently discarded before the user session is issued.

  2. Jun 17, 2026 · NIST NVD

    Updated

    Casdoor versions 2.362.0 and earlier do not enforce SAML assertion time bounds. The gosaml2 library reports all time-validation results, including NotOnOrAfter and NotBefore, in the assertionInfo.WarningInfo field. However, ParseSamlResponse() never reads this field, meaning that time bounds are computed by the library but silently discarded before the user session is issued.

Sources

  • CVE.orgVulnerability recordCVE-2026-9096

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-9096

    30-day exploitation probability 0.4%

    first.org
  • NIST NVDVulnerability recordCVE-2026-9096

    Casdoor versions 2.362.0 and earlier do not enforce SAML assertion time bounds. The gosaml2 library reports all time-validation results, including NotOnOrAfter and NotBefore, in the assertionInfo.WarningInfo field. However, ParseSamlResponse() never reads this field, meaning that

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.