Skip to content

Security: Developmi/multitenant-elt

Security

SECURITY.md

Security policy

Supported versions

Version Supported Notes
2.x ✅ Yes Active release line
1.x ⚠️ Maintenance Critical security fixes only until 2026-12-31
< 1.0 ❌ No Unsupported

Known and Mitigated CVEs

The project enforces proactive supply chain security with Trivy, Syft, and Cosign:

CVE / Identifier Affected Component Status Mitigation Strategy
CVE-2026-109518 Debian 13.7 apt / libapt-pkg7.0 Mitigated Runtime package upgrade in Dockerfile until upstream python:3.12-slim rebuilds.
CVE-2026-27464 Metabase < 0.57.13 Mitigated Image pinned by multi-arch OCI SHA256 digest to v0.57.13.
GHSA-6q48-6c7w-9gw2 certifi Mitigated Upgraded to >= 2026.10.23 in uv.lock.
CVE-2026-114145 gitpython Mitigated Upgraded to >= 3.2.1 in uv.lock.
CVE-2026-114613 msgpack Mitigated Upgraded to >= 1.2.4 in uv.lock.

Reporting a vulnerability

Do not open a public GitHub issue for security vulnerabilities.

Report vulnerabilities privately via one of these channels:

Include in your report:

  • Description of the vulnerability and its potential impact.
  • Steps to reproduce or a proof-of-concept.
  • Affected versions.
  • Any suggested mitigations.

Response timeline

Stage Target time
Acknowledgment 48 hours
Initial assessment 5 business days
Fix or mitigation 30 days (critical: 7 days)
Public disclosure After fix is available

Disclosure policy

This project follows coordinated disclosure. We ask that you give us reasonable time to address the vulnerability before public disclosure. We will credit reporters in the release notes unless anonymity is requested.

Security best practices for this project

  1. Never commit .env files - the .gitignore blocks them; use .env.example as a template
  2. Postgres is bound to 127.0.0.1 only - no public database access
  3. Metabase is opt-in (--profile metabase) and connects with a dedicated read-only role (metabase_reader) that only exists when METABASE_READER_ENABLED=true (OFF by default; see ARCHITECTURE.md → Postgres Users and Access)
  4. Pipeline tokens live in environment variables, never in code
  5. Docker networks scope container traffic; Metabase attaches to the internal net to reach Postgres, so its security boundary is the restricted read-only DB role, not network isolation (see ARCHITECTURE.md → Honest Network Posture)
  6. Telegram alerts use a bot token with minimal permissions

There aren't any published security advisories