# CVE-2026-72846: Lightdash Scheduled Delivery Webhook URLs Are Not Validated, Allowing Server-Side Request Forgery

> Attackers can exploit unvalidated webhook URLs in scheduled deliveries to perform Server-Side Request Forgery against internal services and cloud metadata endpoints.

- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-hw2h-qf3m-2r8v

## What is CVE-2026-72846?

CVE-2026-72846 is a medium-severity server-side request forgery vulnerability in lightdash, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-72846?


## How do I fix CVE-2026-72846?

No fix has been published for CVE-2026-72846 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-72846 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72846 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72846 and fix it if it is affected.

What it is: CVE-2026-72846 is a medium-severity server-side request forgery vulnerability in lightdash, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72846 exists.

Affected product: lightdash. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72846/ (Markdown: https://insights.sbomify.com/CVE-2026-72846/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72846
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72846
- OSV: https://osv.dev/vulnerability/CVE-2026-72846

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72846/
Summaries are generated and may contain mistakes; the official description above is the record.