# CVE-2026-33130: Uptime Kuma: SSTI in Notification Templates Allows Arbitrary File Read (Incomplete Fix for GHSA-vffh-c9pq-4crh)

> Attackers can read arbitrary files on the server via Server-side Template Injection in notification templates due to incomplete path validation.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2026
- **Updated:** 20 Mar 2026

## What is CVE-2026-33130?

CVE-2026-33130 is a medium-severity path traversal vulnerability in louislam uptime-kuma, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program), CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

## Which versions are affected by CVE-2026-33130?

It affects 1 product.


Products: Uptime.kuma Uptime Kuma.

## How do I fix CVE-2026-33130?

No fix has been published for CVE-2026-33130 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33130 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33130 exists.

## Other vulnerabilities in louislam uptime-kuma

- [CVE-2023-44400](https://insights.sbomify.com/CVE-2023-44400/): Uptime Kuma has Persistentent User Sessions (medium 6.7)
- [CVE-2023-49276](https://insights.sbomify.com/CVE-2023-49276/): Attribute Injection leading to XSS(Cross-Site-Scripting) in uptime-kuma (medium 6.3)
- [CVE-2026-32230](https://insights.sbomify.com/CVE-2026-32230/): Uptime Kuma is Missing Authorization Checks on Ping Badge Endpoint, Leaks Ping times of monitors without needing to be on a status page (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33130 and fix it if it is affected.

What it is: CVE-2026-33130 is a medium-severity path traversal vulnerability in louislam uptime-kuma, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33130 exists.

Affected product: louislam uptime-kuma. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33130/ (Markdown: https://insights.sbomify.com/CVE-2026-33130/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33130
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33130
- OSV: https://osv.dev/vulnerability/CVE-2026-33130

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33130/
Summaries are generated and may contain mistakes; the official description above is the record.