Skip to content
Fencer Vulns
medium 5.3

CVE-2026-32230 json

Uptime Kuma is Missing Authorization Checks on Ping Badge Endpoint, Leaks Ping times of monitors without needing to be on a status page

published 2026-03-12 7 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-11665 , GHSA-c7hf-c5p5-5g6h

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 62%
public exploits
0
none known, plus a Nuclei check

Summary

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.

Patch / fix

  • npm uptime-kuma 2.2.0
  • dockge.kuma dockge 2.2.0
  • uptime-kuma_project uptime-kuma 2.2.0
  • uptime.kuma uptime_kuma 2.2.0
  • uptime_kuma_project uptime_kuma 2.2.0

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
7 mo ago

Exploit prediction

0.98% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • Nuclei template Uptime-Kuma < v1.23.0 - Improper Access Control nuclei detection template
  • github.com https://github.com/louislam/uptime-kuma/security/advisories/GHSA-c7hf-c5p5-5g6h referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm uptime-kuma
>=2.0.0, <2.2.0
2.2.0

Affected products

  • louislam uptime-kuma

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.