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 17 March 2025.
- Which products and versions are affected?
- uptime-kuma (npm) SEMVER:introduced=1.23.0,last_affected=2.0.0-dev.0.
- Is there a fix for This vulnerability?
- A patch was published on 2025-01-26: Fix merged into master branch 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, in a network appliance.
- Am I affected?
- Check whether you run uptime-kuma (npm) 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
A Regular Expression Denial of Service (ReDoS) vulnerability exists in Uptime Kuma versions 1.23.0 and later due to inefficient regex patterns used to sanitize notification URLs. Specifically, the application used a greedy regex `\/*$` to strip trailing slashes in components like `pushdeer.js`. An attacker with administrative privileges can provide a crafted string (e.g., a long sequence of slashes followed by a non-slash character) that triggers catastrophic backtracking. This results in 100% CPU utilization and a denial-of-service state for the Node.js event loop. The issue was addressed by implementing a non-backtracking regex pattern.
Affected products
- louislam Uptime Kuma >= 1.23.0, < 2.0.0-dev.0
Timeline
- 2025-01-25: disclosed: Issue reported on GitHub
- 2025-01-26: patched: Fix merged into master branch
- 2025-03-17: advisory: Initial GHSA and CVE published