Skip to content

Lightdash bug bounty programs

lightdash.com Updated

Lightdash runs one public program: a Sorona bug bounty paying up to $1,500.

Top reward
$1,500
Sorona
Programs
1
1 pays cash
Targets in scope
13
2 types
Last change
None yet
Tracked since Nov 2026

Where to report

The one public program Lightdash runs.

Amounts are the top reward per severity in the currency each program pays. First response is the platform's measured average when it publishes one, else what the policy promises.

What is in scope

13 targets. 6 excluded.

  • https://www.lightdash.com

    Web

  • Authentication in full: password login, Google, Okta, Azure AD, OneLogin and generic OIDC, plus the account provisioning and identity linking that follows an assertion

    Products and areas

  • Query generation and execution, covering the explore and metric layer, custom dimensions, custom metrics, filters and the SQL runner

    Products and areas

  • Scheduled deliveries and alerts, which run queries unattended and send results to Slack, email or a webhook a user configured

    Products and areas

  • Server-side rendering for scheduled images and PDFs, where the product loads its own pages in a headless browser

    Products and areas

  • Sharing: share links, public dashboard URLs, embedded dashboards and the signed tokens behind embedding, all of which reach viewers outside the normal permission model

    Products and areas

  • The dbt integration: repository access, the tokens and deploy keys Lightdash holds for GitHub, GitLab, Bitbucket and Azure DevOps, and the project compilation that reads a repository's contents

    Products and areas

  • The full API surface and the session, cookie and CSRF handling in front of it, along with personal access tokens and the service account paths

    Products and areas

  • The organisation, project and space model in full, covering membership, roles, invitations and every check that decides whether a user reaches a dashboard, chart, space or project

    Products and areas

  • The policy asks for any vulnerability report at the project security address and commits to a remediation window rather than declaring a component boundary. The whole product is in scope, and the stale supported-versions table is not a scope statement

    Products and areas

  • The self-hosted deployment path, including the environment configuration and the initial setup flow

    Products and areas

  • The SQL runner specifically, which lets a permitted user write arbitrary SQL against a connected warehouse

    Products and areas

  • Warehouse connection handling for every supported engine, including connection parameters, credential storage, encryption and the connection test path

    Products and areas

No target matches. Try part of a host name, such as the company name.

Out of scope 6

Don't test these. A program can exclude a host another program covers; the program you report to decides.

  • A self-hosted deployment left with default secrets or no authentication in front of it, which is an operator decision

  • Access an organisation admin granted deliberately, including SQL runner rights on a connected warehouse

  • dbt itself and the warehouse engines behind it, each of which has its own vendor process

  • Lightdash Cloud's hosting infrastructure rather than the product code

  • Public GitHub issues, which are not a private channel for a security report

  • Upstream dependencies, unless Lightdash's own use of them is what makes the defect reachable

Recent changes

Reward and scope changes across every Lightdash program, newest first.

No changes recorded yet. New targets and reward moves show up here and in the RSS feed.

Recent CVEs

Published vulnerabilities in Lightdash products, from the NVD.

Search NVD
  • packages/backend/src/routers in Lightdash before 0.510.3 has insecure file endpoints, e.g., they allow .. directory traversal and do not ensure that an intended file extension (.csv or .png) is used.

About this page

This page gathers every public program listed under lightdash.com: platform programs, self-hosted policies and security.txt contacts. Each program's own policy decides what is in scope and what it pays; check it before you test.

Something wrong or missing? Report a correction.