Security fixes are applied to the latest release of the deepguard PyPI package and to the main branch.
| Version | Supported |
|---|---|
| 1.1.x (latest) | ✅ |
| < 1.1 | ❌ |
Please do not open a public issue, pull request, or discussion for security problems.
Report vulnerabilities privately through GitHub: Report a vulnerability (Security tab → Report a vulnerability).
If you cannot use GitHub's private reporting, email seoyunje2001@gmail.com instead.
Please include:
- The affected component (
deepguardpackage,inference/explainability,App/backend,client/frontend, or Docker images) - The version or commit you tested
- Steps to reproduce, or a proof of concept
- The impact you expect (e.g. data exposure, remote code execution, session hijacking)
- We aim to acknowledge your report within 7 days.
- We will keep you updated while we investigate and work on a fix.
- Once a fix is released, we will publish a GitHub Security Advisory and credit you unless you ask us not to.
DeepGuard is maintained by a small student team, so response times may vary. Thank you for helping keep the project safe.
In scope:
- The
deepguard,inference,explainability, andpreprocessPython packages - The FastAPI backend (
App/), including session handling and file uploads - The React frontend (
client/) - Docker images and
docker-compose.ymlpublished from this repository
Out of scope:
- Vulnerabilities in third-party dependencies that are already publicly known (please report them upstream; Dependabot tracks updates here)
- Model evasion or adversarial examples that make a deepfake go undetected — these are research limitations, not security vulnerabilities, and can be reported as regular issues