Casdoor IAM Flaw Breaks Tenant Isolation
An unpatched authorization bypass in Casdoor lets an org-level admin perform administrative actions against other tenants' organizations.
Sourcekb.cert.org — open the original
What to check
- Applies to
- The 1 CVE named below. Whether you run an affected version is not assessed: check the versions the source lists.
- Exploitation
- No exploitation in the wild and no public exploit is recorded for the CVEs named.
CERT/CC has published an advisory for CVE-2026-15630, an authorization bypass affecting the open-source Casdoor IAM platform (versions 3.115.0 and earlier). The flaw arises from a desynchronization between the global authorization filter, which validates requests using the '?id=' URL query parameter, and downstream controllers (e.g., controllers/user.go, controllers/permission.go), which instead act on the 'owner' and 'name' fields in the JSON request body. This mismatch means the object checked for authorization differs from the object actually acted upon, letting an authenticated organization administrator (IsAdmin=true) perform unauthorized administrative operations—such as creating or deleting users, modifying permissions, or disrupting SSO/SAML configurations—against organizations they do not own.
In multi-tenant Casdoor deployments, this breaks the isolation boundary between tenants: a low-privileged organization admin can escalate to affect other organizations, and depending on exposed endpoints and deployment configuration, this could lead to full compromise of the Casdoor instance itself. No vendor patch is currently available, as CERT/CC was unable to coordinate disclosure with the Casdoor maintainers. The vulnerability was reported by Louis Sanchez of Voke Cyber.
Defenders running Casdoor in multi-tenant configurations should treat this as a priority mitigation item given the absence of a patch. Recommended interim measures include minimizing accounts with IsAdmin=true, enforcing MFA on administrative accounts/actions, alerting on cross-organization administrative activity (new admin account creation, cross-tenant user deletion, permissive wildcard Casbin rules), and monitoring for unexplained changes in user counts or administrative objects across organizations.
Mentioned in this report
Source reporting: https://kb.cert.org/vuls/id/889462
Free public brief. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them, no card.
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 16,445 reports from 149 sources, 666 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.
Create a free account What it costs