Description
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.
Published: 2026-08-20
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Lightdash creates scheduled deliveries that POST to a user‑supplied webhook URL. In affected releases, the POST request is performed directly with no validation of the URL, allowing a user who can create or trigger a delivery to supply any private, loopback, or link‑local address. The server will then send the POST request, but it never returns the upstream response to the requester; instead, any error payload is recorded in the server log. This behavior enables an attacker to probe internal network services and potentially interact with protected endpoints such as cloud metadata services, with the ability to distinguish reachable hosts from unreachable ones by the resulting error messages. While the flaw does not directly execute code, it can be leveraged for internal reconnaissance and, if the internal endpoint is vulnerable, for further compromise.

Affected Systems

The vulnerability applies to the open‑source Lightdash product in the version series 1.146.3. It was discovered in the code that handles Google Chat and Microsoft Teams webhook clients. The fix is included in release 1.146.4, which redirects the webhook calls through a validation routine that restricts URLs to public endpoints.

Risk and Exploitability

The CVSS score is 5.3, reflecting moderate severity. EPSS data is unavailable, and the issue is not listed in the CISA KEV catalog. Attackers require permissions to create or trigger a scheduled delivery, so the threat is limited to users with those rights. The attacker can target any internal IP range reachable from the server, including private and link‑local addresses. The exploit does not provide direct code execution but can facilitate internal scanning or interaction with sensitive services, making it a non‑zero‑day risk for systems exposed to privileged users.

Generated by OpenCVE AI on August 21, 2026 at 00:34 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Lightdash to 1.146.4 or later, which adds URL validation for webhook deliveries
  • If an upgrade is not immediately possible, restrict the ability to create or trigger scheduled deliveries to trusted administrators only
  • Monitor the server logs for POST request failures to internal addresses and consider implementing outbound firewall rules that block requests to private or link‑local IP ranges

Generated by OpenCVE AI on August 21, 2026 at 00:34 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 21 Aug 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Fri, 21 Aug 2026 01:30:00 +0000

Type Values Removed Values Added
First Time appeared Lightdash
Lightdash lightdash
Vendors & Products Lightdash
Lightdash lightdash

Thu, 20 Aug 2026 22:15:00 +0000

Type Values Removed Values Added
Description 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.
Title Lightdash Scheduled Delivery Webhook URLs Are Not Validated, Allowing Server-Side Request Forgery
Weaknesses CWE-918
References
Metrics cvssV3_1

{'score': 6.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N'}

cvssV4_0

{'score': 5.3, 'vector': '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'}


Subscriptions

Lightdash Lightdash
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-21T15:39:22.777Z

Reserved: 2026-08-10T15:14:51.467Z

Link: CVE-2026-72846

cve-icon Vulnrichment

Updated: 2026-08-21T15:39:09.937Z

cve-icon NVD

Status : Received

Published: 2026-08-20T22:18:05.400

Modified: 2026-08-21T16:18:16.027

Link: CVE-2026-72846

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-21T01:15:06Z

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)