Solving the DevOps Infrastructure Dilemma: Enabling developer velocity with control 💡

Register for the webinar here →


Bug Bounty

At Spacelift, your security is our first and foremost priority. We run this program to prove and maintain this trust and to keep Spacelift secure. If you have information about a qualified security vulnerability that is within our predetermined scope, we would love to hear from you!

Submit report

Easy rules

The Spacelift bug bounty program accepts vulnerability reports containing original and validated in-scope vulnerabilities that a potential attacker could use to compromise the confidentiality, integrity, and or availability of the Spacelift application. By participating in the Spacelift bounty program, you agree to follow all of the program rules. 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.

  • Bounty

  • Hall of Fame

  • low

    up to


  • medium

    up to


  • high

    up to


  • critical

    up to


Program rules


  • Scope
  • Header
    X-BugBounty with your email address
  • Type

Out of scopes

  • Contact form (especially HubSpot ones)
  • Attacks against any account other than the specified target accounts.
  • Any other Spacelift assets not specifically listed as in-scope.
  • Data breaches or credential dumps.
  • Any communication with Spacelift colleagues.
  • Third-party companies that perform business transactions for Spacelift

Qualifying vulnerabilities

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

Non-qualifying vulnerabilities

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

Reward eligibility

  • Only the preproduction environment is within the scope of the bounty program https://*
  • 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.

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.