LiveActive security incident?Get immediate response
CVE Record

CVE-2026-9098: CVE-2026-9098

In Casdoor versions 2.362.0 and earlier, the SAML callback handler in controllers/auth.go accepts any well-formed SAMLResponse sent to /api/acs without verifying that it corresponds to an AuthnRequest previously issued by Casdoor. Additionally, if an administrator disables or deletes an IdP (Identity Provider) after a SAML flow has started, the handler still processes the response using the provider snapshot loaded at the start of the request. As a result, an attacker controlling a registered upstream IdP can send unsolicited SAML responses, or replay a legitimately captured response in a different session or after the original flow has ended. In both cases, Casdoor accepts the response and issues a session, enabling persistent unauthorized access.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Casdoor can accept SAML login responses without confirming Casdoor started that login. If an attacker controls a registered upstream identity provider, Casdoor may issue a session from an unsolicited or replayed response. This can allow unauthorized access without user interaction.

Executive priority

Prioritize as critical where Casdoor provides authentication for internal or customer-facing systems. Unauthorized session issuance can directly affect confidentiality and integrity, even though availability impact is not emphasized in the CVSS vector.

Technical view

The /api/acs SAML callback in Casdoor 2.362.0 and earlier does not verify SAMLResponse correlation to a prior AuthnRequest. It can also process a provider snapshot even after an IdP is disabled or deleted during a flow. The issue is classified as CWE-346 with CVSS 9.1.

Likely exposure

Organizations using Casdoor 2.362.0 or earlier with SAML and registered upstream IdPs are the likely exposure group. The bundle does not identify other products or deployment-specific prerequisites beyond Casdoor and SAML IdP configuration.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The described risk requires a registered upstream IdP under attacker control, or replay of a legitimately captured response in another session or after the flow ends.

Researcher notes

Evidence is clear on the authentication validation flaw, affected version ceiling, endpoint, and replay/unsolicited-response behavior. Public sources in the bundle do not provide exploit-in-the-wild proof, patch version details, or a complete mitigation procedure.

Mitigation direction

  • Inventory Casdoor deployments and identify versions 2.362.0 or earlier.
  • Check Casdoor and CERT guidance for patched versions or official mitigations.
  • Reduce trust in unnecessary or untrusted upstream SAML IdPs.
  • Review and terminate suspicious SAML-authenticated sessions after remediation.
  • Increase monitoring around /api/acs authentication outcomes.

Validation and detection

  • Confirm whether Casdoor uses SAML authentication in production.
  • Review configured upstream IdPs and who controls them.
  • Check /api/acs logs for sessions lacking expected initiated login state.
  • Verify vendor updates enforce AuthnRequest-to-response correlation.
  • Document any disabled or deleted IdPs tied to recent SAML activity.
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-346: 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-9098 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
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

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

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: total

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
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2026-9098Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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-346 · source CWE mapping

Origin Validation Error

Origin Validation Error represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.