louislam uptime-kuma up to 2.2.0 notification-provider.js require.resolve php file inclusion

Summaryinfo

A vulnerability identified as problematic has been detected in louislam uptime-kuma up to 2.2.0. This impacts the function require.resolve of the file notification-provider.js. Performing a manipulation results in php file inclusion. This vulnerability was named CVE-2026-33130. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in louislam uptime-kuma up to 2.2.0. This affects the function require.resolve of the file notification-provider.js. The manipulation with an unknown input leads to a php file inclusion vulnerability. CWE is classifying the issue as CWE-98. The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions. This is going to have an impact on confidentiality. The summary by CVE is:

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 advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-33130 since 03/17/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available.

Upgrading to version 2.2.1 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-13670). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• louislam

Name

• uptime-kuma

Version

• 2.0
• 2.1
• 2.2.0

Website

• Product: https://github.com/louislam/uptime-kuma/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion