Vulnerability disclosure policy
If you find a security vulnerability in Cloudfleet, report it to us privately so we can fix it before anyone exploits it. This page explains how to report, what is in scope, and how we respond.
How to report
Email [email protected] in English. Include:
- The affected domain, product and version.
- The steps to reproduce the issue, with any proof-of-concept code.
- The impact: what an attacker can read, change or take over, shown with your own accounts and resources.
We act on reports that show a reproducible security impact. We close reports without reproduction steps or a demonstrated impact without a reply.
Scope
In scope:
cloudfleet.aiand its subdomains, including the Cloudfleet Console (console.cloudfleet.ai) and the API (api.cloudfleet.ai).- Cluster endpoints and the container registry under
cloudfleet.dev. - Software you install from Cloudfleet: the Cloudfleet CLI, the Terraform provider, the Cloudfleet plugin for AI agents, and the software Cloudfleet installs on your nodes.
Test only against a Cloudfleet organization and clusters you own.
Out of scope, and closed without a reply:
- Output from automated scanners without a working exploit.
- Missing or weak HTTP security headers, cookie flags or TLS settings without a working exploit.
- SPF, DKIM, DMARC and other email configuration.
- Clickjacking on pages without a sensitive action, and cross-site request forgery on login, logout or forms without security impact.
- Missing rate limits, account or email enumeration, and password policy.
- Version numbers, banners, error messages and public files that disclose no sensitive data.
- Self-XSS, and attacks that need physical access to a device or an already compromised account.
- Denial of service, social engineering, spam and physical attacks.
- Vulnerabilities in third-party services that Cloudfleet uses. Report them to the vendor.
- Workloads that customers run on their own clusters.
What we commit to
- We acknowledge an in-scope report within 3 business days.
- We tell you whether we accept the report, and keep you informed until the fix is released.
- We coordinate publication with you. Keep the details private until we release a fix, or for 90 days after your report, whichever comes first. If a fix needs more time, we agree a new date with you.
- We credit you in the advisory if you want to be named.
Safe harbor
If you research in good faith and follow this policy, we consider your research authorized. We do not take legal action against you or file a criminal complaint. Good faith means that you:
- Access only the data you need to show the vulnerability, and do not keep or share it.
- Stop and report as soon as you reach data that belongs to another customer.
- Do not disrupt the service, for example with load tests, denial of service or spam.
- Do not use the vulnerability for anything other than showing it to us.
No bug bounty
Cloudfleet does not run a bug bounty program and does not pay for reports. A report that asks for payment, or makes disclosure depend on payment, is not made in good faith.
Security advisories
We evaluate the impact of every CVE identified in the components Cloudfleet uses. Most do not affect Cloudfleet and our customers, and routine updates cover the rest, so we do not announce them individually.
When a vulnerability can affect your clusters or data, we notify affected customers directly. After the fix is released, we also publish it in the release notes. If the vulnerability is in software you install from Cloudfleet, we request a CVE for it.
The contact address and this policy are also published in /.well-known/security.txt, as defined in RFC 9116.
← Confidential Control Plane