Quick answers
- Is CVE-2026-6815 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-6815 being exploited in the wild.
- How severe is CVE-2026-6815?
- Medium severity, with a CVSS score of 5.9, published 11 May 2026.
- Which products and versions are affected?
- Casbin Casdoor up to (including) 2.328.0; github.com/casdoor/casdoor (Go) <= 1.1000.0, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.1000.0.
- Is there a fix for CVE-2026-6815?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-6815 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-6815?
- Check whether you run Casbin Casdoor or github.com/casdoor/casdoor (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability (CWE-22) exists in Casdoor's Local File System storage provider within the /api/upload-resource endpoint. The application fails to sanitize the 'pathPrefix' and 'fullFilePath' parameters, allowing an authenticated attacker with file upload privileges to use directory traversal sequences (e.g., ../../) to write or overwrite files outside the designated $CASDOOR/files/ directory. This can result in the corruption of the backend database (casdoor.db), persistence via cron job creation, or full host compromise depending on the service account's permissions. While a pull request (PR #5458) has been submitted to address the issue, no official patched version was confirmed at the time of the advisory.
Affected products
- Casdoor Casdoor <= 1.1000.0
Identifiers
- CVE-2026-6815
- GHSA-rmxx-v9rj-vpvg
- GO-2026-5945
Timeline
- 2026-02-23: other: Vendor notified
- 2026-05-11: disclosed: Initial public disclosure
- 2026-05-11: advisory: GitHub Advisory published