CVE-2026-72846
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 18% of all known CVEs.
References
Related Vulnerabilities
Other CWE-918 (Server-Side Request Forgery (SSRF)) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-21893 | High | 8.2 | 100% | KEV + Ransom | - |
| CVE-2021-40438 | Critical | 9.0 | 100% | KEV + Ransom | Fix |
| CVE-2021-34473 | Critical | 9.1 | 100% | KEV + Ransom | Fix |
| CVE-2021-21985 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2021-26855 | Critical | 9.1 | 100% | KEV + Ransom | Fix |
| CVE-2022-41040 | High | 8.8 | 100% | KEV + Ransom | Fix |
Common questions
How do I fix CVE-2026-72846?
No published fix for CVE-2026-72846 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-72846 being actively exploited?
Not that we know of. CVE-2026-72846 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.26% is the estimated probability that it will be exploited in the next 30 days. That is higher than 18% of all scored CVEs.
How severe is CVE-2026-72846?
CVE-2026-72846 has a CVSS v3 base score of 6.4, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-72846
Markdown
[](https://tridentstack.com/cve/CVE-2026-72846)HTML
<a href="https://tridentstack.com/cve/CVE-2026-72846"><img src="https://tridentstack.com/cve/badge/CVE-2026-72846.svg" alt="CVE-2026-72846"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-21.