LiveActive security incident?Get immediate response
CVE Record

CVE-2026-9096: CVE-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 time bounds are computed by the library but silently discarded before the user session is issued.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Casdoor may accept SAML login assertions even when their valid time window has expired or has not started. For organizations using Casdoor for SAML single sign-on, this weakens a core session control and may let stale assertions result in sessions. The source bundle does not show confirmed active exploitation.

Executive priority

Treat as high priority for any Casdoor-backed SAML SSO environment. Prioritize internet-facing or broadly used identity deployments because authentication control failures can affect many downstream applications.

Technical view

In Casdoor 2.362.0 and earlier, gosaml2 reports SAML NotOnOrAfter and NotBefore validation results in WarningInfo, but ParseSamlResponse() does not read that field before issuing a user session. The library computes time-bound warnings, but Casdoor silently discards them.

Likely exposure

Exposure is most likely where Casdoor 2.362.0 or earlier is deployed and SAML authentication is enabled. The bundle does not identify affected configurations beyond Casdoor and SAML response parsing.

Exploitation context

The CVSS vector indicates network reachability, low complexity, no privileges, and no user interaction. The bundle marks KEV as false and provides no cited evidence of active exploitation.

Researcher notes

Evidence is specific to SAML assertion time-bound handling. The source bundle does not provide a named fixed version, exploit proof, or observed exploitation. Avoid assuming non-SAML Casdoor deployments are affected without vendor confirmation.

Mitigation direction

  • Inventory Casdoor deployments and confirm exact running versions.
  • Check CERT and Casdoor vendor guidance for fixed versions or official mitigations.
  • Upgrade or apply vendor-provided remediation when available and tested.
  • Temporarily reduce reliance on affected SAML flows where business risk justifies it.
  • Monitor authentication logs for unusual SAML session issuance patterns.

Validation and detection

  • Confirm whether Casdoor is version 2.362.0 or earlier.
  • Determine whether SAML login is enabled for each Casdoor deployment.
  • Review release notes or vendor advisories before declaring remediation complete.
  • Verify logs show expected SAML authentication behavior after remediation.
  • Document compensating controls if immediate upgrade is not possible.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-613: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-9096 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-9096Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
CasdoorCasdoor0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-613 · source CWE mapping

Insufficient Session Expiration

Insufficient Session Expiration represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.