Security fixes are provided for the latest release on the main branch. Older tags and forks are not supported unless a release note explicitly says so.

Do not open a public issue for a suspected vulnerability. Report it privately to the repository maintainers using GitHub's private vulnerability reporting feature. Include a concise description, affected version or commit, reproduction steps, impact, and any suggested mitigation. Do not include real credentials, personal data, or production data.

Maintainers target an acknowledgement within 5 business days, an initial severity assessment within 10 business days, and coordinated remediation or a status update within 30 days. These are targets, not a guarantee; the report will be kept private until a coordinated disclosure is agreed.

This policy covers the MESA source repository, published Python package, and the Docker image built from this repository. Deployment-specific credentials, third-party LLM accounts, and self-managed infrastructure remain the operator's responsibility.

The unreleased v4 API resolves authorization as principal → tenant → workspace → dataset → agent → server-created session. Agent IDs are compute/persona context and are not standalone tenant credentials. Purge and rollback require explicit dataset permissions.

V4 API credentials are issued as key_id.secret; only salted scrypt digests are stored. Plaintext is displayed once by mesa-v4-admin. Reports must never include credentials, source content, claim tokens or production data.

V3 remains a compatibility surface with its historical agent/session partitioning. A v3 isolation control must not be represented as a v4 tenant/dataset guarantee.