2.1 KiB
Security Policy
Our primary goal is to ensure the protection and confidentiality of sensitive data stored by users on open-webui.
Supported Versions
| Version | Supported |
|---|---|
| main | ✅ |
| others | ❌ |
Reporting a Vulnerability
We appreciate the community's interest in identifying potential vulnerabilities. However, effective immediately, we will not accept low-effort vulnerability reports. To ensure that submissions are constructive and actionable, please adhere to the following guidelines:
-
No Vague Reports: Submissions such as "I found a vulnerability" without any details will be treated as spam and will not be accepted.
-
In-Depth Understanding Required: Reports must reflect a clear understanding of the codebase and provide specific details about the vulnerability, including the affected components and potential impacts.
-
Proof of Concept (PoC) is Mandatory: Each submission must include a well-documented proof of concept (PoC) that demonstrates the vulnerability. If confidentiality is a concern, reporters are encouraged to create a private fork of the repository and share access with the maintainers to maintain privacy. Reports lacking valid evidence will be disregarded.
-
Proposed Solutions: We expect submissions to include actionable suggestions for remediation. Reports without a proposed fix will not be accepted.
Submissions that do not meet these criteria will be closed, and repeat offenders may face a ban from future submissions. We aim to create a respectful and constructive reporting environment, and low-effort submissions hinder that goal.
Product Security
We regularly audit our internal processes and system architecture for vulnerabilities using a combination of automated and manual testing techniques. We are also planning to implement SAST and SCA scans in our project soon.
For immediate concerns or detailed reports that meet our guidelines, please create an issue in our issue tracker or contact us on Discord.
Last updated on 2024-08-06.