Live › vulnerability › CVE-2026-61654
Lightdash's dbt Cloud webhook endpoint has no authentication or signature check, so anyone who knows a project's UUID can post to it and create previews. Path traversal through the accountId and runId values can also change the URL that Lightdash requests from cloud.getdbt.com with the project's API key in the Authorization header.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 22:27 UTC. All times on this page are UTC.
Teams running self-hosted or shared Lightdash at or before 0.3213.0 that connect a dbt Cloud IDE project through the dbt Cloud webhook. Exposure also depends on an attacker knowing the project UUID, which is not enumerable but can leak in shared or multi-tenant setups. Teams on 0.3214.0 or later, or without the dbt Cloud webhook, can skip this.
No product ranges from the sources yet.
0.3213.0 are affected.dbt Cloud IDE connection with the dbt Cloud webhook POST /api/v1/projects/{projectUuid}/dbt-cloud/webhook enabled.0.3214.0 or later, which fixes the identifier path traversal and verifies webhook HMAC signatures when a secret is configured.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-61654")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.