Quick answers
- Is CVE-2026-72846 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72846 being exploited in the wild.
- How severe is CVE-2026-72846?
- Medium severity, with a CVSS score of 6.4, published 20 August 2026.
- Which products and versions are affected?
- Lightdash before 1.146.4.
- Is there a fix for CVE-2026-72846?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-72846 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-72846?
- Check whether you run Lightdash at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a Server-Side Request Forgery (SSRF) in the webhook delivery mechanism. The GoogleChatClient.ts and MicrosoftTeamsClient.ts modules store user-supplied webhook URLs and later issue POST requests via fetch() without validation. The validatePublicHttpUrl helper that is used elsewhere in the codebase to prevent SSRF is not applied to webhook URLs, which carry no server-side constraint. An authenticated user able to create or trigger a scheduled delivery can craft a webhook URL pointing to private IP ranges, loopback addresses, link-local addresses, or cloud metadata endpoints. While response bodies are not directly returned to the attacker, error messages are logged server-side, allowing the attacker to enumerate reachable internal services. The vulnerability is fixed in version 1.146.4, which routes webhook requests through postSchedulerWebhook with proper validation.
Affected products
- Lightdash Lightdash before 1.146.4
Timeline
- 2026-08-20: disclosed