Do not open a public GitHub issue for security vulnerabilities. Public disclosure before a fix is ready puts all users at risk.
Report vulnerabilities privately via GitHub Security Advisories.
You will receive a response within 5 business days acknowledging the report. We aim to release a fix within 30 days for critical issues and 90 days for lower-severity issues, depending on complexity.
- A clear description of the vulnerability and the affected component
- Steps to reproduce (or a proof-of-concept)
- Potential impact and severity assessment
- Any suggested mitigations
Components in scope:
- FastAPI backend (
/api/v1/*,/mcp) - Authentication flow — generic OIDC sign-in (
oidc-client-ts) + backend token validation, email OTP sign-in (ADR 0032: code request/verify,dq_sess_cookie sessions, signup allowlist, rate limits), and personal access tokens - Frontend container (nginx SPA — the sole public surface, proxying
/api+/mcp) - Celery worker + check execution path (GX, Snowflake DMF, Databricks DQX job submission — ADR 0036)
- The optional LLM provider seam (ADR 0042) and what it sends to a configured provider
- Secret-store access patterns (the
SecretStoreseam; validated implementations: Azure Key Vault, AWS Secrets Manager, OpenBao/Vault KV v2 — ADR 0039) - The
dataq-clientPython package anddataqCLI (packages/dataq-client)
Out of scope:
- Vulnerabilities in third-party dependencies — report those upstream; we track them via Dependabot
- Issues requiring physical access to the infrastructure a deployment runs on
DataQ follows Semantic Versioning, with releases tagged in this repository and curated in CHANGELOG.md.
| Version | Supported |
|---|---|
main (latest commit) |
Yes — fixes land here first |
| Latest tagged release (currently v1.2.0) | Yes |
| Older tagged releases | No |
Security fixes are applied to main and ship in the next release. There is no long-term
support branch and no backporting to superseded tags — if you are running an older tag,
upgrade to the latest release to pick up a fix.