# CVE-2026-61576: Lightdash: Unauthenticated dbt Cloud webhook with path injection leaks API key


- **Severity:** High 8.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026

## What is CVE-2026-61576?

CVE-2026-61576 is a high-severity vulnerability in lightdash, published on 29 Oct 2026. 

### Official 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-61576?


## How do I fix CVE-2026-61576?

No fix has been published for CVE-2026-61576 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-61576 being exploited?

There is no known exploitation of CVE-2026-61576 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61576 and fix it if it is affected.

What it is: CVE-2026-61576 is a high-severity vulnerability in lightdash, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-61576 in the wild and no public exploit code.

Affected product: lightdash. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-61576/ (Markdown: https://insights.sbomify.com/CVE-2026-61576/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-61576
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-61576
- OSV: https://osv.dev/vulnerability/CVE-2026-61576

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-61576/
Summaries are generated and may contain mistakes; the official description above is the record.