Vulnerability in Louislam Uptime-Kuma
CVE-2026-33130
Uptime Kuma is an open source, self-hosted monitoring tool. In versions 1.23.0 through 2.2.0, the fix from GHSA-vffh-c9pq-4crh doesn't fully work to preventServer-side Template Injection (SSTI). The three mitigations added to the Liquid engine (root, relativeReference, dynamicPartials) only block quoted paths. If a project uses an unquoted absolute path, attackers can still read any file on the server. The original fix in notification-provider.js only constrains the first two steps of LiquidJS's file resolution (via root, relativeReference, and dynamicPartials options), but the third step, the require.resolve() fallback in liquid.node.js has no containment check, allowing unquoted absolute paths like /etc/passwd to resolve successfully. Quoted paths happen to be blocked only because the literal quote characters cause require.resolve('"/etc/passwd"') to throw a MODULE_NOT_FOUND error, not because of any intentional security measure. This issue has been fixed in version 2.2.1.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
EPSS 0.004, 33.3th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Louislam Uptime-Kuma — versions >= 1.23.0, < 2.2.1
- Uptime.kuma Uptime Kuma
Weakness classification (CWE)
References
- https://github.com/louislam/uptime-kuma/security/advisories/GHSA-v832-4r73-wx5j (Exploit, Mitigation, Vendor Advisory)
- https://github.com/advisories/GHSA-vffh-c9pq-4crh (Exploit, Mitigation, Vendor Advisory)
- https://github.com/louislam/uptime-kuma/releases/tag/2.2.1 (Product, Patch)