dbcve.org
VulnerabilityAwaiting classification

CVE-2026-9093

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Casdoor versions 2.362.0 and earlier, the SAML service provider implementation does not validate the AudienceRestriction element in SAML assertions. The buildSp function in object/saml_sp.go never sets AudienceURI on the gosaml2 SAMLServiceProvider struct and never inspects WarningInfo.NotInAudience. This allows assertions issued for other service providers to be accepted by Casdoor.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Casdoor's SAML SP implementation fails to validate the AudienceRestriction element in SAML assertions. The buildSp function does not set the AudienceURI property on the gosaml2 SAMLServiceProvider struct and does not check WarningInfo.NotInAudience, allowing authentication assertions issued for other service providers to be accepted.

MitigationConfigure AudienceURI in the SAML SP settings and implement validation to reject assertions where WarningInfo.NotInAudience is true, ensuring only assertions explicitly intended for this Casdoor instance are accepted.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SAML provider is configured in Casdoor
    Review Casdoor's SAML authentication settings. Navigate to the SAML identity provider configuration page in the Casdoor admin console, or inspect the Casdoor database/configuration files for SAML provider entries.
    Affected if A SAML identity provider is connected to Casdoor and users can authenticate via SAML.
  2. Locate the SAML Service Provider buildSp function
    Search the Casdoor codebase for the buildSp function that constructs the gosaml2 SAMLServiceProvider struct. This is typically found in SAML-related source files.
    Affected if The buildSp function exists in the Casdoor codebase and is used for SAML authentication.
  3. Verify AudienceURI is set on the SAMLServiceProvider
    Inspect the buildSp function code to determine if the AudienceURI property is assigned a value. Check if the code sets sp.AudienceURI or equivalent to a specific audience value corresponding to this Casdoor instance.
    Affected if The AudienceURI property is not set or remains empty/unassigned in the SAMLServiceProvider configuration.
  4. Check for WarningInfo.NotInAudience validation
    Search the SAML authentication response handling code for checks on WarningInfo.NotInAudience or similar audience validation logic. Determine if assertions are rejected when NotInAudience is true.
    Affected if There is no validation code that rejects SAML assertions where WarningInfo.NotInAudience evaluates to true.
  5. Review SAML assertion processing for audience restriction
    Examine the code path that processes incoming SAML assertions after authentication. Look for any audience validation that compares the assertion's AudienceRestriction against the expected audience for this Casdoor service provider.
    Affected if SAML assertions are accepted without verifying that the AudienceRestriction element matches this specific Casdoor instance.

A Casdoor instance is affected if it has SAML authentication configured and the buildSp function does not set AudienceURI or the code does not check and reject assertions where WarningInfo.NotInAudience is true.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure AudienceURI in the SAML SP settings and implement validation to reject assertions where WarningInfo.NotInAudience is true, ensuring only assertions explicitly intended for this Casdoor instance are accepted.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9093 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9093 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data