Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-72846Published 2026-08-20

CVE-2026-72846 — lightdash

medium

As of 2026-08-21, CVE-2026-72846 is a MEDIUM-severity vulnerability in lightdash, CVSS v3.1 6.4, EPSS 0.2% (18.2th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-72846 as of 2026-08-21; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
6.4/10Medium
EPSS
0.2%Higher than 18.2% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
3.9/10Threadlinqs triage score
Published
Updated 2026-08-21
CVSS v3.1 6.4 (MEDIUM) · CVSS v4.0 5.3 · EPSS 0.2% (higher than 18.2% of all scored CVEs) · Priority 3.9/10 · Published 2026-08-20

Last updated:

What is CVE-2026-72846?

Lightdash stores the webhook URL supplied with a scheduled delivery and later posts to it from sendWebhook in packages/backend/src/clients/GoogleChat/GoogleChatClient.ts and in packages/backend/src/clients/MicrosoftTeams/MicrosoftTeamsClient.ts. In affected versions both call fetch on the stored URL directly. The validatePublicHttpUrl helper in packages/backend/src/utils/ssrfProtection.ts, used for MCP server URLs, is not applied on either path, and the webhook fields carry no server-side URL constraint. A user able to create or trigger a scheduled delivery can therefore direct the server to issue POST requests to private, loopback and link-local addresses, including cloud metadata endpoints, and can distinguish reachable internal services from unreachable ones through the resulting errors. The upstream response is never returned to the requester; on a failure status its body is written to the server log instead. Version 1.146.4 routes both clients through postSchedulerWebhook from packages/backend/src/utils/schedulerWebhookValidation rather than calling fetch directly.

The record classifies CVE-2026-72846 under weakness class CWE-918. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 46 days ago.

Severity and exploitation probability

CVSS v3.1 base score
6.4 — MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
CVSS v4.0 base score
5.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
EPSS (FIRST)
0.2% probability of exploitation in the next 30 days, higher than 18.2% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
3.9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-08-20, last modified 2026-08-21

Is CVE-2026-72846 being exploited?

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

Affected products and versions

  • lightdash: lightdash

How to fix CVE-2026-72846

No vendor patch reference has been recorded for CVE-2026-72846 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-72846

No threat campaign in the Threadlinqs corpus currently references CVE-2026-72846, 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, FIRST EPSS. Last verified by Threadlinqs on .

Vendor advisory and patch

Technical analysis

Third-party advisory

Issue tracking and product pages