Skip to content

GHSA-rgq2-93gj-ffxg CVE-2026-9096 GO-2026-5899

Casdoor doesn't enforce SAML assertion time bounds

High Go
Severity
7.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.33%
Chance of exploitation in the next 30 days. Higher than 26.24% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-613 Insufficient Session Expiration
Fix
None yet
No fixed version published

Description

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.

Affected versions

Go

PackageVulnerableFixed in
github.com/casdoor/casdoor
<= 1.1000.1-0.20260321120606-239e8bd69487
No fix yet
github.com/casdoor/casdoor
all versions
No fix yet

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 3.1 7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Weakness

CWE-613: Insufficient Session Expiration

According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."

How to prevent it
  • Implementation: Set sessions/credentials expiration date.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-mfvp-7p3v-x9mh
Casdoor SAML callback handler accepts any well-formed SAMLResponse sent to /api/acs without verifying that it corresponds to an AuthnRequest
Critical Also affects github.com/casdoor/casdoor
GHSA-339w-3hqm-9pjc
Casdoor doesn't verify that a JWT used for token exchange is still active
Critical Also affects github.com/casdoor/casdoor
GHSA-c9w5-qp6m-m395
Casdoor: GetTokenExchangeToken bypass through lack of cross-organization JWT signature check
Critical Also affects github.com/casdoor/casdoor
GHSA-3w4h-g9f5-j84p
Casdoor does not validate the AudienceRestriction element in SAML assertions
Critical Also affects github.com/casdoor/casdoor
GHSA-gv4m-v8c8-hr3g
Casdoor allows users to bypass configured MFA requirements
Medium Also affects github.com/casdoor/casdoor
GHSA-fwgq-j9r9-qjgr
Casdoor has an authentication bypass
Critical Also affects github.com/casdoor/casdoor
GHSA-rmxx-v9rj-vpvg
Casdoor: Arbitrary file write possible through Local File System storage provider
Medium Also affects github.com/casdoor/casdoor
GHSA-p8c7-hjc4-gwf8
Casdoor vulnerable to SSRF via crafted Webhook URL
High Also affects github.com/casdoor/casdoor
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor