Authenticated SSRF via unvalidated webhook URLs
Published Aug 20, 2026 · Updated Aug 20, 2026
Server-side request forgery in scheduled deliveries in Lightdash before 1.146.4 allows remote authenticated users to reach internal services via webhook URLs. The GoogleChatClient.sendWebhook and MicrosoftTeamsClient.sendWebhook paths pass stored Google Chat and Microsoft Teams webhook URLs to fetch without validatePublicHttpUrl or equivalent server-side constraints, so private, loopback, link-local, and metadata addresses are accepted. An Editor or higher user who can create or trigger a scheduled delivery can make the Lightdash server issue POST requests and infer internal reachability from success and error behavior, while response bodies are not returned to the requester except that failed responses are logged.
Summary
What happened
Server-side request forgery in scheduled deliveries in Lightdash before 1.146.4 allows remote authenticated users to reach internal services via webhook URLs. The GoogleChatClient.sendWebhook and MicrosoftTeamsClient.sendWebhook paths pass stored Google Chat and Microsoft Teams webhook URLs to fetch without validatePublicHttpUrl or equivalent server-side constraints, so private, loopback, link-local, and metadata addresses are accepted. An Editor or higher user who can create or trigger a scheduled delivery can make the Lightdash server issue POST requests and infer internal reachability from success and error behavior, while response bodies are not returned to the requester except that failed responses are logged.
The record
- CVE
- CVE-2026-72846
- Published
- Aug 20, 2026
- Updated
- Aug 20, 2026
- Vendor
- Lightdash
- Product
- Lightdash
- Classifications
- CWE-918, T1046
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 20, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.146.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo