OneRAG is an open-source RAG system that may process private documents, prompts, chat messages, and operational metadata. Please report security issues privately and avoid publishing proof-of-concept exploits until a fix is available.

Security fixes are prioritized for:

• The main branch.
• The latest tagged release, when releases are available.

Older branches are handled on a best-effort basis unless a maintainer explicitly marks them as supported.

Use GitHub's private vulnerability reporting or Security Advisory flow for this repository. If private reporting is unavailable, open a minimal public issue that says a security report is available, but do not include secrets, credentials, exploit steps, private data, or payloads in the public issue.

Please include:

• Affected version, commit SHA, or deployment mode.
• Impacted component, such as API auth, PII handling, file ingestion, retrieval, frontend, CI, Docker, or dependency supply chain.
• Reproduction steps that use dummy data only.
• Expected impact and any known mitigations.

• Critical: acknowledge within 2 business days and prioritize an emergency fix.
• High: acknowledge within 3 business days and target the next patch window.
• Medium/Low: triage within 5 business days and schedule with normal maintenance work.

OneRAG should not require production secrets for local tests, CI validation, or quickstart demos. Demo access codes, example API keys, and sample data must not be treated as production credentials. Any change that weakens authentication, PII masking, file validation, dependency pinning, or CI verification needs an explicit security note in the pull request.