🛡️ CVE-2026-32230 — uptime-kuma

🟡 CVSS 5.3 — Medium ⚠️ Exploit Public CWE-862 OSV
5.3
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

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

Summary

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.

Affected Code

File: server/routers/api-router.js, approximately line 304

The ping badge endpoint directly calls UptimeCalculator.getUptimeCalculator(requestedMonitorId) without first checking if the monitor is public. Compare with the status badge endpoint (~line 148) which correctly queries:

```sql

SELECT monitor_group.monitor_id FROM monitor_group, group

WHERE monitor_group.group_id = group.id

AND monitor_group.monitor_id = ?

AND public = 1

```

Protected vs Vulnerable Endpoints

| Endpoint | Has public=1 check? |

|----------|-------------------|

| /api/badge/:id/status | Yes |

| /api/badge/:id/uptime/:duration? | Yes |

| /api/badge/:id/avg-response/:duration? | Yes |

| /api/badge/:id/cert-exp | Yes |

| /api/badge/:id/response | Yes |

| /api/badge/:id/ping/:duration? | No — vulnerable |

PoC

1. Install Uptime Kuma (tested on latest v2 stable via Docker)

2. Create an HTTP(s) monitor (e.g., monitoring http://localhost:3001)

3. Do NOT add the monitor to any public status page or group

4. Wait for heartbeats to accumulate (~5 minutes)

5. Query unauthenticated:

```bash

curl http://localhost:3001/api/badge/1/status → returns N/A (correct, monitor is private)

curl http://localhost:3001/api/badge/1/ping/24 → returns "Avg. Ping (24h): 10ms" (LEAKED)

```

Impact

An unauthenticated attacker can:

  • Enumerate private monitor IDs
  • Extract average response time data for private monitors
  • Infer existence and reachability of internal monitored services

Suggested Fix

Add the same public monitor check before the UptimeCalculator call:

```javascript

let publicMonitor = await R.getRow(`

SELECT monitor_group.monitor_id FROM monitor_group, \group\

WHERE monitor_group.group_id = \group\.id

AND monitor_group.monitor_id = ?

AND public = 1

`, [requestedMonitorId]);

if (!publicMonitor) {

badgeValues.message = "N/A";

badgeValues.color = badgeConstants.naColor;

}

```

<img width="1228" height="710" alt="Screenshot 2026-02-24 at 4 49 40 PM" src="https://github.com/user-attachments/assets/80aeae2d-be08-449f-8b39-c50da7aaedba" />

<img width="1271" height="770" alt="File Alons til View He" src="https://github.com/user-attachments/assets/d50c9a00-282a-4b79-b5e1-f77afde9223a" />

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity none, availability none.

Weakness class

CVE-2026-32230 is classified as CWE-862: Missing Authorization. No authorisation check is performed before carrying out a restricted action.

Affected software

CVE-2026-32230 is recorded against 1 package.

  • uptime-kuma

Timeline and source

Published on 12 March 2026 and last revised on 17 June 2026. A public exploit is known to exist, which raises the urgency of patching considerably. A vendor advisory or fix has been published. Record sourced from OSV.

References

github.com (Web)
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Web)
github.com (Web)
github.com (Package)
github.com (Web)

Details

Severity MEDIUM
CVSS Score 5.3
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CWE CWE-862
Public Exploit ⚠️ Yes
Source OSV
Published 2026-03-12
Updated 2026-08-12
Modified 2026-06-17

Affected Packages

Software From version Fixed in
uptime-kuma

Similar Threats

Exploit Protection

Are you running uptime-kuma?

CVE-2026-32230 carries CVSS 5.3 Medium rating and a public exploit already exists. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.

Check My Site For CVE-2026-32230 →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026