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

Q: How do I fix CVE-2026-32230?

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

Q: Is CVE-2026-32230 being exploited?

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

Q: What does CVE-2026-32230 affect?

CVE-2026-32230 affects uptime kuma. Severity is medium (CVSS 5.3). Uptime Kuma is an open source, self-hosted monitoring tool. From 2.0.0 to 2.1.3 , the GET /api/badge/:id/ping/:duration? endpoint in server/routers/api-router.js does not verify that the requested monitor belongs to a public group. All othe

Q: How urgent is CVE-2026-32230?

Priority 43/100. Public exploit reference; Remotely exploitable, no login, no user action

This week

MEDIUM 5.3REMOTEUPGRADE

CVE-2026-32230 is a medium-severity flaw (CVSS 5.3) 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. From 2.0.0 to 2.1.3 , the GET /api/badge/:id/ping/:duration? endpoint in server/routers/api-router.js does not verify that the requested monitor belongs to a public group. All other badge endpoints check AND public = 1 in their SQL query before returning data. The ping endpoint skips this check entirely, allowing unauthenticated users to extract average ping/response time data for privat

Why this priority

Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 40%)
CISA exploited list	No
Weakness	CWE-862
Published	2026-03-12
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: uptime.kuma

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

Am I affected?

Timeline

2026-03-12 19:16 UTCPublished CVE record published
2026-06-17 10:35 UTCUpdated Record last modified

uptime.kuma uptime kuma UPGRADE

Affected: >= 2.0.0 and < 2.2.0

Fixed in: 2.2.0

Safe to downgrade to: a release before 2.0.0

1. Check installed version

apt-cache policy uptime-kuma || rpm -q uptime-kuma || uptime-kuma --version

2. UPGRADE to 2.2.0 (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 2.0.0 (Debian / Ubuntu)

apt-cache madison uptime-kuma sudo apt install uptime-kuma=<VERSION_BEFORE_2.0.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_2.0.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.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Nuclei scan template: Uptime-Kuma < v1.23.0 - Improper Access Control

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-32230?

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

Is CVE-2026-32230 being exploited?

CVE-2026-32230 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-32230 affect?

CVE-2026-32230 affects uptime kuma. Severity is medium (CVSS 5.3). Uptime Kuma is an open source, self-hosted monitoring tool. From 2.0.0 to 2.1.3 , the GET /api/badge/:id/ping/:duration? endpoint in server/routers/api-router.js does not verify that the requested monitor belongs to a public group. All othe

How urgent is CVE-2026-32230?

Priority 43/100. Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-33130 MEDIUM 6.5 UPGRADE Uptime Kuma is an open source, self-hosted monitoring tool
CVE-2023-49805 MEDIUM 6.0 UPGRADE UPGRADE Uptime Kuma is an easy-to-use self-hosted monitoring tool
CVE-2023-49804 MEDIUM 6.7 UPGRADE UPGRADE Uptime Kuma is an easy-to-use self-hosted monitoring tool
CVE-2023-49276 MEDIUM 6.3 UPGRADE Uptime Kuma is an open source self-hosted monitoring tool
CVE-2023-44400 MEDIUM 6.7 UPGRADE Uptime Kuma is a self-hosted monitoring tool

References

← Back to latest CVEs