VeraRAG is currently pre-1.0. Security fixes target the main branch.

Please do not open a public issue for secrets exposure, authentication bypasses, code execution, path traversal, or unsafe file handling. Report privately to the maintainer listed in the repository metadata, or open a private security advisory on GitHub if available.

Include:

• affected commit or release;
• reproduction steps;
• impact and affected component;
• whether any API keys, local files, or user data may be exposed.

• Do not commit .verarag_key, SQLite databases, environment files, API keys, or raw private corpora.
• Web UI API keys are encrypted locally, but this is not a hosted multi-tenant security boundary.
• Demo and benchmark outputs may include model responses and document excerpts; review them before publishing.
• Run make security before commits and make security-local on local workstations when ignored .env.local files may exist. For CI systems that ingest code-scanning reports, use verarag-scan-secrets --sarif. The GitHub Actions workflow preserves a secret-scan.sarif artifact even when the hard secret gate fails, so maintainers can inspect redacted locations.
• If a real key is pasted into chat, committed, pushed, or written to logs, treat it as compromised: revoke or rotate it in the provider console, remove it from the source location, rerun verarag-scan-secrets --include-ignored, and avoid reusing the old value in future evaluations.