CVE-2026-61576 lightdash · lightdash

Lightdash: Unauthenticated dbt Cloud webhook with path injection leaks API key

Vulnerability at a glance

Severity, exploitation likelihood & attack requirements

CVSS v4.0 severity
8.3High
EPSS · exploitation likelihood
Not available No score available
EPSS trend
UnavailableNo comparable history
Known exploitation
Not in KEV CISA KEV catalog Absence does not establish safety
Attack vector
NetworkRemotely reachable
Attack complexity
LowFewer obstacles to exploitation
Privileges required
NoneNo authentication required
User interaction
NoneNo user action needed
Exploit availability & maturity
Not scored Availability not established No explicit exploit maturity assessment View exploit evidence
How to read the colors & trend
Higher exposureElevatedModerateLower exposureUnknown / unassessed

CVSS colors follow its reported severity. Attack-factor colors describe each requirement, not an overall risk rating. Gray also covers absence from KEV; absence does not establish safety.

EPSS display bands: below 1% blue, 1–10% amber, 10–50% orange, 50% and above red. These are presentation bands, not FIRST severity categories. The trend compares daily EPSS probabilities, not percentile ranks; “pp” means percentage points. The sparkline shows relative movement, with its vertical scale fitted to the observed scores.

Already protected by existing Atomicorp rules No new CVE-specific rule required.

Atomicorp ModSecurity protection

Protected by Atomicorp rules

Atomicorp ModSecurity rules block attacks exploiting this vulnerability. Keep your rules current.

By targeting underlying attack techniques and CWE weakness classes, existing rules can protect against newly disclosed vulnerabilities. Rule changes are regression-tested against attack and false-positive corpora.

3 rules identified Verified 2026-10-30 View rules & research details →

WAF protection does not change the CVSS or EPSS score. Keep your software patched and your Atomicorp rules current.

CISA SSVC

No CISA SSVC assessment is available in the current source data.

On this page

CVE Details

  • Protection status: Protected by Atomicorp rules · About protection statuses
  • CVE: CVE-2026-61576
  • Name: Lightdash: Unauthenticated dbt Cloud webhook with path injection leaks API key
  • Severity: High
  • CVSS: 8.3 (v4.0) (High)
  • CVSS version: 4.0
  • CVSS source: GitHub_M CNA
  • CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
    • Attack vector: Network
    • Attack complexity: Low
    • Attack requirements: Present
    • Privileges required: None
    • User interaction: None
    • Vulnerable-system confidentiality: High
    • Vulnerable-system integrity: Low
    • Vulnerable-system availability: None
    • Subsequent-system confidentiality: Negligible
    • Subsequent-system integrity: None
    • Subsequent-system availability: None
    • Safety: Not defined
  • CWE: CWE-22
  • Vendor: lightdash
  • Vulnerable product: lightdash
  • CVE published: 2026-10-29
  • CVE last modified: 2026-10-29
  • Latest Update: 2026-10-30
  • Selected Rule IDs observed: 340007 , 344360 , 390709
  • Matching rules: 3; rules with blocking actions: 3
  • Would-block Rule IDs: 340007 , 344360 , 390709
  • Request surfaces inspected: JSON request data, Request argument names, Request arguments, Request cookies, Request filename, SOAP request data, XML request data
Technical vulnerability details · CVSS assessments, exploit evidence & CPE data

CVSS assessments

CVSS v4.0 · security-advisories@github.com

  • Base score: 8.3
  • Base severity: HIGH
  • Assessment type: Secondary
  • Source identifier: security-advisories@github.com
  • Full vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
    • Attack vector: Network
    • Attack complexity: Low
    • Attack requirements: Present
    • Privileges required: None
    • User interaction: None
    • Vulnerable-system confidentiality: High
    • Vulnerable-system integrity: Low
    • Vulnerable-system availability: None
    • Subsequent-system confidentiality: Negligible
    • Subsequent-system integrity: None
    • Subsequent-system availability: None
    • Safety: Not defined
  • Exploit maturity: Not scored

Exploitability and impact subscores describe the vulnerability’s technical characteristics. Exploit maturity describes the reported state of exploitation; these are separate measures.

Assessment source: NVD record · CVE record

Vulnerable CPE configurations

No vulnerable CPE configurations are supplied in the current NVD record. See the affected-product information and vendor guidance on this page.

Vulnerability Description

Lightdash is an open source business intelligence platform. In affected versions through 0.3213.0, the dbt Cloud webhook POST /api/v1/projects/{projectUuid}/dbt-cloud/webhook has no authentication middleware or signature validation. In packages/backend/src/controllers/projectController.ts, testWebhook() accepts accountId and runId from a job.run.completed request and passes them to createPreviewWithExplores() in packages/backend/src/services/ProjectService/ProjectService.ts. These unsanitized values are interpolated into the server-side dbt Cloud API URL, which is requested with the victim project’s API key in the Authorization header. Path traversal through accountId changes the requested path on cloud.getdbt.com without changing its host, so the credential-bearing request reaches an attacker-influenced path on that fixed host. The advisory claims API-key theft, but the supplied evidence does not establish that the attacker can observe the Authorization header. The unauthenticated webhook also allows preview creation. The target must be a dbt Cloud IDE project and the attacker must know its projectUuid; the UUID is not enumerable but can be discovered in shared or multi-tenant contexts. Version 0.3214.0 fixes identifier path traversal and verifies webhook HMAC signatures only when a secret is configured; without a secret, unsigned webhooks continue to be processed.

  1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (340007 , 344360 , 390709 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

  2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

    • Affected versions: lightdash version < 0.3214.0.
    • No specific CNA/vendor solution or workaround is included in the current CVE Record . Review the vendor’s security advisories and supported-release guidance before making changes.

  3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

Test or Research Source

  • Source: Atomicorp AI Research Framework
  • Tags: cve, derived, traversal, waf-probe

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

  • Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
  • Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
  • Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
  • Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
  • Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ .