Vulnerability Disclosure Program

Security is core to our values, and we appreciate the input of security researchers acting in good faith to help us maintain a high standard for the security and privacy of our users, which includes encouraging responsible vulnerability research and disclosure. This policy sets out our definition of good faith in the context of finding and reporting vulnerabilities, as well as what you can expect from us in return.

Note: This is a non-award program. We do not offer monetary bounties for reports.

Official Channels

Report any vulnerability you believe is in scope by emailing security@okteto.com. Please include enough detail for us to reproduce the issue: the affected asset, steps to reproduce, and the impact you believe it has.

Use this address rather than contacting individual Okteto employees, opening a public GitHub issue, or posting in a shared Slack channel. Please keep all discussion of an unfixed vulnerability within that email thread.

Expectations

When working with us, according to this policy, you can expect us to:

Acknowledge receipt of your report within five business days;
Extend Safe Harbor for your vulnerability research that is related to this policy;
Work with you to understand and validate your report; and
Work to remediate discovered vulnerabilities in a timely manner, keeping you informed as we go.

Guidelines

To encourage vulnerability research and to avoid any confusion between legitimate research and malicious attack, we ask that you attempt, in good faith, to:

Play by the rules. Adhere to this policy and any other relevant agreements, such as our Terms of Service;
Report any vulnerability you have discovered promptly;
Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
Use only the Official Channels to discuss vulnerability information with us;
Handle the confidentiality of details of any discovered vulnerabilities according to this policy;
Perform testing only on in-scope systems, and respect systems and activities which are out of scope;
If a vulnerability provides unintended access to user data, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information, cease testing and submit a report immediately;
Only interact with accounts you own unless given explicit permission by the account holder;
Do not engage in extortion;
Be clear and succinct, a short proof of concept link is invaluable;
Never attempt non-technical attacks, such as social engineering, phishing, or physical attacks, against our employees, users, or infrastructure; and
Do not view, alter, save, store, transfer, or otherwise access our data or the data of our users without explicit permission.

We may modify the terms of this program or terminate it at any time.

Safe Harbor

When conducting vulnerability research according to this policy, we consider that research to be:

Authorized in view of any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good faith violations of this policy;
Authorized in view of relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;
Exempt from restrictions in the Acceptable Use section of our Terms of Service that would interfere with conducting security research, and we waive those restrictions on a limited basis; and
Lawful, helpful to the overall security of the Internet, and conducted in good faith.

You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you, and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report before going any further.

In Scope

Any design or implementation issue that substantially affects the confidentiality or integrity of user data is likely to be considered in scope. The following assets are in scope:

www.okteto.com and the web properties we operate on the okteto.com domain;
The Okteto CLI, at github.com/okteto/okteto;
The Okteto Platform container images and Helm chart that we distribute.

Common examples of the issues we prioritize:

Cross-site scripting.
Cross-site request forgery.
Mixed-content scripts.
Authentication or authorization flaws.
Server-side code execution bugs.
Circumvention of our permissions model.
SQL injection.
XML external entity attacks.

This list reflects the research we prioritize and should not be considered exhaustive. Any report that concerns the possible compromise of sensitive user data or our systems is of interest. By extension, this includes serious security weaknesses in any dependency, such as open source libraries, software, or third-party components, actively used in the development of the assets listed above.

Out of Scope

Okteto runs in our customers' own infrastructure. An Okteto installation operated by a customer is that customer's system, not ours, and we cannot authorize testing against it. Do not test any Okteto installation other than one you own.

The following issues are explicitly outside the scope of this program:

Policies on the presence or absence of SPF, DKIM, DMARC, MTA-STS, or CAA records.
Password, email and account policies, such as email id verification, reset link expiration, and password complexity.
Logout cross-site request forgery.
Attacks requiring physical access to a user's device.
Cross-site scripting on any site other than those listed as in scope.
Attacks that require an exploitation tool to overlay on top of our app, for example tapjacking.
Vulnerabilities that require a potential victim to install non-standard software or otherwise take active steps to make themselves susceptible.
Vulnerabilities affecting users of outdated browsers or platforms.
Social engineering of our employees or contractors.
Any physical attempts against our property or data centers.
Presence of the autocomplete attribute on web forms.
Missing cookie flags on non-sensitive cookies.
Any access to data where the targeted user needs to be operating a rooted mobile device.

The following issues are outside the scope of our program unless they are accompanied by evidence of exploitability:

Use of a known-vulnerable library.
Missing best practices.
Insecure SSL/TLS ciphers.
Missing security headers which do not directly lead to a vulnerability.
Lack of CSRF tokens, except when there is evidence of a sensitive user action not protected by a token.
Host header injections.
Reports from automated tools or scans that have not been manually validated.
Presence of banner or version information, unless it identifies a vulnerable version.

Known Issues

Issues already known to us are considered out of scope, though a new report of a known issue may be accepted if the instances described were not previously observed.

Acknowledgments

We are grateful to the security researchers who have made Okteto safer by reporting vulnerabilities to us responsibly. Because this is a non-award program, public credit is the recognition we can offer, and we offer it gladly.

We credit a researcher when their report was valid, in scope, not already known to us, and resulted in a change on our side. If your report meets that bar, we will ask whether you would like to be listed here and under what name. Listing is always your choice, and we are glad to keep your report anonymous if you prefer.

2026

BINARLY REsearch team, for reporting an exposed HashiCorp Terraform API token embedded in a published container image (BRLY-2026-036).
artemisa, for reporting a read-only CMS API token exposed in a client-side JavaScript bundle.

2022

imwaiting18, for reporting a dangling social media link on our about page that allowed an attacker to impersonate an Okteto employee.