# CVE-2026-6815: CVE-2026-6815

> An authenticated admin can exploit path traversal in Casdoor's file storage to write arbitrary files, potentially leading to code execution or data modification.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-rmxx-v9rj-vpvg, GO-2026-5945

## What is CVE-2026-6815?

CVE-2026-6815 is a medium-severity path traversal vulnerability in Casdoor, published on 11 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An arbitrary file write vulnerability exists in Casdoor's Local File System storage provider. Due to insufficient path sanitization, an authenticated attacker with administrative privileges can perform a Path Traversal attack to create or overwrite arbitrary files anywhere on the host filesystem, bypassing the application's intended storage sandbox.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

3 open source packages ship an affected version, including github.com/casdoor/casdoor. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/casdoor/casdoor` | Go | All versions | None |
| `github.com/casdoor/casdoor` | Go | All versions to 1.1000.0 | None |
| `github.com/casdoor/casdoor` | Go | All versions to 1.1000.0 | None |

Products: Casbin Casdoor.

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

Upgrade to a fixed version.

## Is CVE-2026-6815 being exploited?

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

Public exploit code:

- Proof of Concept (PoC) exploit for CVE-2026-6815: Authenticated Path Traversal & Arbitrary File Write in Casdoor (< 3.54.1) leading to RCE/DoS. (github_poc): https://github.com/danilo-dellorco/CVE-2026-6815
- Casdoor 3.54.1 - Arbitrary File Write via Path Traversal (exploitdb)

## Other vulnerabilities in Casdoor

- [CVE-2022-38638](https://insights.sbomify.com/CVE-2022-38638/): Casdoor arbitrary file write vulnerability (critical 9.1)
- [CVE-2024-41657](https://insights.sbomify.com/CVE-2024-41657/): GHSL-2024-035: Casdoor CORS misconfiguration (high 8.1)
- [CVE-2022-44942](https://insights.sbomify.com/CVE-2022-44942/): Casdoor arbitrary file deletion vulnerability via uploadFile function (high 8.1)
- [CVE-2024-41264](https://insights.sbomify.com/CVE-2024-41264/): casdoor's use of`ssh.InsecureIgnoreHostKey()` disables host key verification (high 7.5)
- [CVE-2022-24124](https://insights.sbomify.com/CVE-2022-24124/): SQL Injection in Casdoor (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6815 is a medium-severity path traversal vulnerability in Casdoor, published on 11 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6815 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/casdoor/casdoor (Go): affected all versions; no fix listed
- github.com/casdoor/casdoor (Go): affected all versions up to 1.1000.0; no fix listed
- github.com/casdoor/casdoor (Go): affected all versions up to 1.1000.0; no fix listed

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-6815/ (Markdown: https://insights.sbomify.com/CVE-2026-6815/index.md)
```

## Sources

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

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