CVE-2026-9093

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-28. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (CERT/CC) lists Casdoor versions up to and including 2.362.0 as affected. No release containing a fix is confirmed on record.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 28, 2026

Last Modified

June 2, 2026

Advisory Details (1)

Auto-updated Oct 8, 2026
No fix on record yet. Sources: cert.
CERT

VU#780781 - Casdoor contains multiple authentication bypass and access management vulnerabilities

https://kb.cert.org/vuls/id/780781

Vendor Advisories for CVE-2026-9093(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/casdoor/casdoor—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/casdoor/casdoor—
  • every version through 1.1000.1-0.20260321120606-239e8bd69487: no fix on record
  • every version on: no fix on record
—

Data Freshness Timeline

(refreshed 20× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 379 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 281 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-10-16 12:57 UTCEG score recompute
  3. 2026-10-16 12:57 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-10-15 13:52 UTCEG score recompute
  6. 2026-10-15 13:51 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-10-14 08:45 UTCEG score recompute
  9. 2026-10-14 08:45 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-13 04:13 UTCEG score recompute
  12. 2026-10-13 04:13 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-10-12 14:46 UTCEG score recompute
  15. 2026-10-12 05:08 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-11 19:13 UTCEG score recompute
  17. 2026-10-11 16:30 UTCEG score recompute
  18. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-10-11 13:45 UTCEG score recompute
  20. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  22. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  23. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  24. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  25. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.5% · 39th percentile
Show 73 more
  1. 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  5. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  6. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  7. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  9. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  10. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  18. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  19. 2026-09-14 06:42 UTCEG score recompute
  20. 2026-09-14 06:42 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-09-13 16:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  22. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  23. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  24. 2026-09-11 09:38 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  25. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  26. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  27. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  28. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  29. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  30. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  31. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  32. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  33. 2026-08-30 19:18 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  34. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  35. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  36. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  37. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  38. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  39. 2026-08-25 04:42 UTCEG score recompute
  40. 2026-08-25 04:41 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-08-24 14:18 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  42. 2026-08-23 23:53 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-08-23 18:42 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-08-23 14:29 UTCEG score recompute
  45. 2026-08-23 14:29 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  47. 2026-08-22 00:39 UTCEG score recompute
  48. 2026-08-22 00:39 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  50. 2026-08-21 20:25 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-08-21 15:26 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-08-21 02:30 UTCEG score recompute
  53. 2026-08-21 02:30 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  55. 2026-08-20 21:51 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-08-20 17:37 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-08-20 10:46 UTCEG score recompute
  58. 2026-08-20 10:46 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  60. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  61. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  62. 2026-08-17 12:41 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-08-17 08:01 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-08-16 15:14 UTCEG score recompute
  65. 2026-08-16 15:14 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  67. 2026-08-16 11:00 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-08-16 06:47 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-08-16 02:34 UTCEG score recompute
  70. 2026-08-16 02:34 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-08-16 02:15 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  72. 2026-08-15 02:28 UTCEG score recompute
  73. 2026-08-15 02:28 UTCGHSA enrichmentGHSA-3w4h-g9f5-j84p · GitHub severity CRITICAL · GitHub CVSS 9.8

Related CVEs(same product)

Frequently asked(5)

What is CVE-2026-9093?
CVE-2026-9093 is a critical-severity vulnerability; its CVE record was published on May 28, 2026. 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…
When was the CVE record for CVE-2026-9093 published?
The CVE record for CVE-2026-9093 was published on May 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 2, 2026; the record at its source may have been updated since.
Is CVE-2026-9093 actively exploited?
CVE-2026-9093 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-9093?
CVE-2026-9093 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-9093?
No fix for CVE-2026-9093 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (CERT/CC) lists Casdoor versions up to and including 2.362.0 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-9093 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-9093

Explore →

Is Your Infrastructure Affected by CVE-2026-9093?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs