Skip to content

Gitpod

By Gitpod GmbH Vulnerability disclosure program on Self-hosted gitpod.io

Accepting reports Full safe harbor security.txt
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
6
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

This program does not pay cash rewards.

Pays cash
No Ona does not currently operate a bug bounty program. There is no monetary compensation or formal recognition program for security vulnerability reports.
Safe harbor
Full Authorized concerning any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy;
Hall of fame
Yes Publicly acknowledge your security research if responsibly disclosed.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

6 assets you may test, 1 excluded.

Domains 3

  • app.gitpod.io
  • com.gitpod-dev.com No bounty
  • io.gitpod No bounty

Wildcard domains 3

  • com.gitpod-dev.com.*
  • com.gitpod-staging.*
  • io.gitpod.*
Out of scope (1)
  • Assets or other equipment not owned by parties participating in this policy.

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Gitpod's policy. "We" in these lines means the program, not this site.

While testing

  • Report any vulnerability you’ve 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;
  • Provide us with a reasonable amount of time (at least 90 days from the initial report) to resolve the issue before you disclose it publicly;
  • Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope;
  • Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept;
  • You should only interact with test accounts you own or with explicit permission from the account holder; and
  • Do not engage in extortion.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 5 hours ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.