CVE-2026-33130 | louislam uptime-kuma up to 2.2.0 notification-provider.js require.resolve filename control (EUVD-2026-13670)

VDB-352053 · CVE-2026-33130 · EUVD-2026-13670 LOUISLAM UPTIME-KUMA UP TO 2.2.0 NOTIFICATION-PROVIDER.JS REQUIRE.RESOLVE FILENAME CONTROL HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.3 $0-$5k 3.54+ 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 filename control. 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 filename control 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). 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 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 5.4 VulDB Meta Temp Score: 5.3 VulDB Base Score: 4.3 VulDB Temp Score: 4.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 6.5 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Filename control CWE: CWE-98 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: uptime-kuma 2.2.1 Timelineinfo 03/17/2026 CVE reserved 03/20/2026 +3 days Advisory disclosed 03/20/2026 +0 days VulDB entry created 03/20/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Status: Confirmed CVE: CVE-2026-33130 (🔒) GCVE (CVE): GCVE-0-2026-33130 GCVE (VulDB): GCVE-100-352053 EUVD: 🔒 Entryinfo Created: 03/20/2026 11:13 Updated: 03/20/2026 12:34 Changes: 03/20/2026 11:13 (64), 03/20/2026 12:34 (1) Complete: 🔍 Cache ID: 99:639:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸