Goblet's default configuration is unsafe for multi-tenant deployments with private repositories.

Default cache keys include only repository URL, not user identity. This allows authenticated users to access cached private repositories belonging to other users.

Severity: Critical (CVSS 8.1) Impact: Private repository data leakage between users/tenants

✅ Your deployment is SAFE if:

• Single user or service account per Goblet instance
• Only public repositories accessed
• Using sidecar pattern (one instance per workload)

🚨 Your deployment is AT RISK if:

• Multiple users share a Goblet instance
• Users access private repositories with different permissions
• Multi-tenant SaaS, Terraform Cloud, or security scanning scenarios

Deploy one Goblet instance per workload. No code changes required:

kubectl apply -f examples/kubernetes-sidecar-secure.yaml

Complete guide: docs/security/multi-tenant-deployment.md

• Security Overview: docs/security/README.md
• Isolation Strategies: docs/security/isolation-strategies.md
• Deployment Guide: docs/security/multi-tenant-deployment.md

Do not open public GitHub issues for security vulnerabilities.

Email: security@example.com

Include:

• Description of vulnerability
• Steps to reproduce
• Affected versions
• Suggested remediation (optional)

We follow a 90-day coordinated disclosure policy.

Security updates are published in:

• CHANGELOG.md
• GitHub Security Advisories
• Security mailing list (subscribe at security@example.com)

1. Never share Goblet instances across tenants without isolation
2. Always use TLS for production deployments
3. Enable audit logging for compliance requirements
4. Review security documentation before deploying
5. Monitor for unauthorized access attempts

• Complete Security Guide
• Deployment Patterns
• Getting Started

Last Updated: 2025-11-07