Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-61654Published 2026-10-29

CVE-2026-61654 — lightdash

high (derived)

As of 2026-10-29, CVE-2026-61654 is a High-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in lightdash, CVSS v4.0 8.3, EPSS 0.3% (32.0th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-61654 as of 2026-10-29; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v4.0
8.3/10High (derived)
EPSS
0.3%Higher than 32.0% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
5.4/10Threadlinqs triage score
Published
CVSS v4.0 8.3 (High, derived from score) · EPSS 0.3% (higher than 32.0% of all scored CVEs) · Priority 5.4/10 · Published 2026-10-29

Last updated:

What is CVE-2026-61654?

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.

The record classifies CVE-2026-61654 under weakness class CWE-89. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 21 days ago.

Severity and exploitation probability

CVSS v4.0 base score
8.3 — High (derived from score)
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
EPSS (FIRST)
0.3% probability of exploitation in the next 30 days, higher than 32.0% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
5.4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-10-29

Is CVE-2026-61654 being exploited?

It currently carries a trending score of 37 in the Threadlinqs vulnerability feed.

Affected products and versions

  • lightdash: lightdash

How to fix CVE-2026-61654

No vendor patch reference has been recorded for CVE-2026-61654 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-61654

No threat campaign in the Threadlinqs corpus currently references CVE-2026-61654, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Other references