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.

The following products are affected by CVE-2026-33130 vulnerability.

Here, you will find a curated list of external links that provide in-depth information to CVE-2026-33130.

URL	Resource
https://github.com/advisories/GHSA-vffh-c9pq-4crh
https://github.com/louislam/uptime-kuma/releases/tag/2.2.1
https://github.com/louislam/uptime-kuma/security/advisories/GHSA-v832-4r73-wx5j