# CVE-2026-9092: CVE-2026-9092

> Attackers can take over accounts by supplying unverified email claims from upstream providers due to missing verification checks in Casdoor.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-qq8g-36vc-g254

## What is CVE-2026-9092?

CVE-2026-9092 is a critical authentication bypass vulnerability in Casdoor, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Casdoor versions 2.362.0 and earlier contain a vulnerability involving unverified email binding that may enable account takeover. The getExistUserByBindingRule function matches users by email without checking the email_verified claim from upstream providers; the idp.UserInfo struct does not even include a EmailVerified field. An attacker can supply an unverified email claim from an upstream provider to take over accounts that use the same email address.

## Which versions are affected by CVE-2026-9092?


## How do I fix CVE-2026-9092?

No fix has been published for CVE-2026-9092 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9092 being exploited?

There is no known exploitation of CVE-2026-9092 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9092 and fix it if it is affected.

What it is: CVE-2026-9092 is a critical authentication bypass vulnerability in Casdoor, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9092 in the wild and no public exploit code.

Affected product: Casdoor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9092/ (Markdown: https://insights.sbomify.com/CVE-2026-9092/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9092
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9092
- OSV: https://osv.dev/vulnerability/CVE-2026-9092

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9092/
Summaries are generated and may contain mistakes; the official description above is the record.