Bug bounty

Spacelift.io - Bug Bounty Program

Spacelift is a sophisticated CI/CD platform for Terraform, CloudFormation, Pulumi, and Kubernetes


Hall of fame


Avg reward
Max reward

Supported languages


1st response
< 1 day
Reports last 24h
Reports last week
Reports this month


Please keep the testing scope only spacelift.dev is included
Please do not test the contact forms (especially HubSpot one)

Features in 20% Bonus scope

  1. Native K8S workers to manage these worker pools efficiently and K8S operators to manage Spacelift resources.
    Reference: https://docs.spacelift.io/vendors/kubernetes/getting-started
    Reference: https://docs.spacelift.io/integrations/kubernetes/operator

  2. The OIDC-based API keys can be used as an alternative to secret-based ones today.
    Reference: https://docs.spacelift.io/integrations/api.html#oidc-based-api-keys

  3. The MFA feature allows you to protect your external IdP session using security keys (FIDO2) managed in Spacelift. Even if your IDP account is compromised, it brings your identity as the last line of defense.
    Reference: https://spacelift-user-documentation-pr-396.onrender.com/product/security/mfa.html#multi-factor-authentication-mfa

For those features, all payouts will be increased by 20%

Bounty Program

At Spacelift, your security is our first and foremost priority. We're aware of the utmost importance of security in our service, and we're grateful for your trust. Here's what we're doing to earn and maintain this trust and to keep Spacelift secure by design. If you have information about a qualified security vulnerability that is within our predetermined scope, we would love to hear from you!

In-scope vulnerabilities will be rewarded based on severity following remediation. The Spacelift private bug bounty program accepts vulnerability reports containing original and validated vulnerabilities that a potential attacker could use to compromise the confidentiality, integrity, and or availability of the services in scope. By participating in the Spacelift private bounty program you agree to follow all of the requirements below. We look forward to working with you to find security vulnerabilities in order to keep our businesses and customers safe. We’ll try to keep you informed about our progress throughout the process.


We offer a reward for every report of a security problem that was not yet known to us. The amount of the reward will be determined based on the severity of the leak and the quality of the report. Our rewards are based on severity per CVSS v3.0 (the Common Vulnerability Scoring Standard). Please note these are general guidelines and that reward decisions are up to the discretion of Spacelift.

Program Rules

Testing Policy and Responsible Disclosure

Please adhere to the following rules while performing research on this program:

  • Don't contact/send payloads against contact forms (especially HubSpot ones), there are people behind - it's annoying.
  • Denial of service (DoS) attacks on Spacelift.io applications, servers, networks or infrastructure are strictly forbidden.
  • Avoid tests that could cause degradation or interruption of our services.
  • Do not use automated scanners or tools that generate a large amounts of network traffic.
  • Do not leak, manipulate, or destroy any user data or files in any of our applications/servers.
  • Do not copy any files from our applications/servers and disclose them.
  • No vulnerability disclosure, full, partial, or otherwise, is allowed.

Reward Eligibility

  • Only the preproduction environment is within the scope of the bounty program https://*.spacelift.dev/
  • Do not collect any personally identifiable information or authentication information from other Spacelift clients.
  • Do not destroy or alter discovered data.
  • Do not inappropriately store Spacelift information in public locations, i.e., GitHub.
  • Do not intentionally harm other users as well as their experience.
  • Do not publicly or privately disclose any vulnerabilities belonging to Spacelift - existing or remediated – to anyone other than Spacelift.
  • Only submit vulnerability reports using the YesWeHack platform.
  • A bounty is only eligible for a payout if the exploited vulnerability is unknown and can be reproduced.
  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
  • Submit one vulnerability per the report unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur, we only award the first report received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  • Social engineering (e.g., phishing, vishing, smishing) is prohibited.
  • Limit automation/rate scraping to 100 requests per minute.
  • Employers/Contractors can participate, excluding functionalities/code written by themself.

Submission Requirements

Reward amounts are based on:

  • Reward grid of the report's scope
  • CVSS scoring and actual business impact of the vulnerability upon performing risk analysis

You can check our documentation here


Asset value CVSS


ScopeTypeAsset value
https://*.app.spacelift.dev web-application
Native K8S workers and operator application
OIDC-based API keys application
MFA application

Out of scopes

  • Session keeps using old user group permissions if user group permissions are changed during a given session's lifespan
  • Contact form (especially HubSpot ones)
  • Any other Spacelift assets not specifically listed as in-scope.
  • Any communication with Spacelift colleagues.
  • Attacks against any account other than the specified target accounts.
  • Data breaches or credential dumps.
  • Third-party companies that perform business transactions for Spacelift

Vulnerability types

Qualifying vulnerabilities

  • SQL Injection (SQLi)
  • Exploitable Cross-Site Scripting (XSS)
  • Remote Code Execution (RCE) after container escape
  • Horizontal and vertical privilege escalation
  • Authentication bypass & broken authentication
  • Business Logic Errors vulnerability with real security impact
  • Local files access and manipulation (LFI, RFI, XXE, XSPA)
  • Cross-Origin Resource Sharing (CORS) with real security impact
  • Cross-site Request Forgery (CSRF) with real security impact
  • Open Redirect

Non-qualifying vulnerabilities

  • Remote Code Execution (RCE) on the worker level.
  • Importing executable files is possible by design. However, working PoC against the application will be accepted
  • All SSRFs are currently excluded from the scope as we are redesigning the way of handling them.
  • Tabnabbing
  • Missing cookie flags
  • Content/Text injections
  • Mixed content warnings
  • Clickjacking/UI redressing
  • Denial of Service (DoS) attacks
  • Known CVEs without working PoC
  • Open ports without real security impact
  • Social engineering of staff or contractors
  • Presence of autocomplete attribute on web forms
  • Vulnerabilities affecting outdated browsers or platforms
  • Self-XSS or XSS that cannot be used to impact other users
  • Outdated libraries without a demonstrated security impact
  • Any hypothetical flaw or best practices without exploitable PoC
  • Expired certificate, best practices and other related issues for TLS/SSL certificates
  • Unexploitable vulnerabilities (ex: XSS or Open Redirect in HTTP Host Header)
  • Reports with attack scenarios requiring MITM or physical access to victim's device
  • Missing security-related HTTP headers which do not lead directly to a vulnerability
  • Unauthenticated / Logout / Login and other low-severity Cross-Site Request Forgery (CSRF)
  • Invalid or missing SPF (Sender Policy Framework), DKIM, DMARC records
  • Session expiration policies (no automatic logout, invalidation after a certain time or after a password change)
  • Disclosure of information without direct security impact (e.g. stack traces, path disclosure, directory listings, software versions, IP disclosure, 3rd party secrets)
  • CSV injection
  • HTTP Strict Transport Security Header (HSTS)
  • Subdomain takeover without a full working PoC
  • Blind SSRF without direct impact (e.g. DNS pingback)
  • Lack of rate-limiting, brute-forcing or captcha issues
  • User enumeration (email, alias, GUID, phone number)
  • Recently disclosed 0-day vulnerabilities (less than 30 days since patch release)
  • Password reset token leak on trusted third-party website via Referer header (eg Google Analytics, Facebook…)

Hunting requirements

Account access

Spacelift.dev App

Please use your GitHub, Google, Gitlab, or Microsoft account associated with YesWeHack email aliases, which are available here for account creation.

We ask you to include the email as an email-alias in the X-BugBounty header.

User agent

Please append to your user-agent header the following value: ' X-BugBounty-email-alias '.

Hunters collaboration

When submitting new report, you can add up to 5 collaborators, and define the reward split ratio.

For more information, see help center.
Note: For reports that have already been rewarded, it is not possible to redistribute the rewards.