What’s Vulnerable › Vulnerabilities

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

• Severity: medium (CVSS 5.3 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.9% probability of exploitation in the next 30 days
• Public exploit or detection template: yes
• Published: 2026-03-12 · updated 2026-06-17
• Weakness: CWE-862

Description

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 private monitors. This vulnerability is fixed in 2.2.0.

Affected products

• Uptime.Kuma Uptime Kuma: from 2.0.0 before 2.2.0 — fixed in 2.2.0

How to fix

Upgrade to a fixed version: Uptime.Kuma Uptime Kuma 2.2.0. Check the vendor advisory for mitigations.

References

• https://github.com/louislam/uptime-kuma/commit/303a609c05d0b174a5045c90f53c2b557d4febae
• https://github.com/louislam/uptime-kuma/issues/7038
• https://github.com/louislam/uptime-kuma/issues/7135
• https://github.com/louislam/uptime-kuma/releases/tag/2.2.0
• https://github.com/louislam/uptime-kuma/security/advisories/GHSA-c7hf-c5p5-5g6h
• https://github.com/louislam/uptime-kuma/security/advisories/GHSA-c7hf-c5p5-5g6h

Get alerted when CVE-2026-32230 or the next vulnerability affects your stack