Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Low severity, with a CVSS score of 3.1, published 20 October 2025.
- Which products and versions are affected?
- Louis Lam Uptime Kuma 1.23.0 through 1.23.16, 2.0.0-beta.4 and earlier.
- Is there a fix for This vulnerability?
- A patch was published on 2025-10-20: Patched in versions 1.23.17 and 2.0.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network.
- Am I affected?
- Check whether you run uptime-kuma (npm). 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 Template Injection (SSTI) in Uptime Kuma's renderTemplate() function, which instantiates a Liquid template engine and processes user-controlled input without sanitization or sandboxing. In notification types such as Webhook and Telegram, user-editable fields are passed directly to renderTemplate(), allowing attackers to inject malicious Liquid template syntax (e.g., {% render '/etc/passwd' %}). An authenticated user with notification configuration permissions can craft a custom webhook body containing template injection payloads to read arbitrary files from the server. The attack requires authentication but no further user interaction. Patches are available in versions 1.23.17 and 2.0.0.
Affected products
- Louis Lam Uptime Kuma 1.23.0 through 1.23.16, 2.0.0-beta.4 and earlier
Timeline
- 2025-10-20: disclosed
- 2025-10-20: patched: Patched in versions 1.23.17 and 2.0.0