Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-33130: Uptime Kuma is an open source, self-hosted monitoring tool

35
Routine
MEDIUM 6.5UPGRADE

CVE-2026-33130 is a medium-severity flaw (CVSS 6.5) affecting uptime kuma. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

  • Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score6.5 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.3% (top 72%)
CISA exploited listNo
WeaknessCWE-98, CWE-1336
Published2026-03-20
Last modified2026-06-17
Publisher (CNA): GitHub, Inc. · Vendor: uptime.kuma

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

uptime.kuma uptime kuma UPGRADE
Affected: >= 1.23.0 and < 2.2.1
Fixed in: 2.2.1
Safe to downgrade to: a release before 1.23.0
1. Check installed version
apt-cache policy uptime-kuma || rpm -q uptime-kuma || uptime-kuma --version
2. UPGRADE to 2.2.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade uptime-kuma
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade uptime-kuma
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.23.0 (Debian / Ubuntu)
apt-cache madison uptime-kuma sudo apt install uptime-kuma=<VERSION_BEFORE_1.23.0> sudo apt-mark hold uptime-kuma
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list uptime-kuma sudo dnf downgrade uptime-kuma-<VERSION_BEFORE_1.23.0> sudo dnf versionlock add uptime-kuma
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-33130?

uptime kuma: upgrade to 2.2.1. Exact commands for each OS are on this page.

Is CVE-2026-33130 being exploited?

CVE-2026-33130 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-33130 affect?

CVE-2026-33130 affects uptime kuma. Severity is medium (CVSS 6.5). 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 eng

How urgent is CVE-2026-33130?

Priority 35/100. Public exploit reference

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.