Is CVE-2026-32230 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-32230 being exploited in the wild.

How severe is CVE-2026-32230?

Low severity, with a CVSS score of 3.1, published 12 March 2026.

Which products and versions are affected?

uptime-kuma (npm) SEMVER:introduced=2.0.0,fixed=2.2.0.

Is there a fix for CVE-2026-32230?

Yes. uptime-kuma (npm): upgrade to 2.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-32230 attacked?

It is attacked over the network.

Am I affected by CVE-2026-32230?

Check whether you run uptime-kuma (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-32230: Uptime Kuma missing authorization check on ping badge endpoint

CVE-2026-32230 · Severity: low · CVSS 3.1 · Published 2026-03-12

Uptime Kuma is an open-source server monitoring tool that displays application availability and performance metrics via embeddable status badges. An unauthenticated attacker can query a specific API endpoint to extract average ping times for monitors that should be private, revealing the existence and response characteristics of internal services without authorization.

Technologies: uptime-kuma (npm). Vendors: npm.

Quick answers

Is CVE-2026-32230 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-32230 being exploited in the wild.
How severe is CVE-2026-32230?: Low severity, with a CVSS score of 3.1, published 12 March 2026.
Which products and versions are affected?: uptime-kuma (npm) SEMVER:introduced=2.0.0,fixed=2.2.0.
Is there a fix for CVE-2026-32230?: Yes. uptime-kuma (npm): upgrade to 2.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-32230 attacked?: It is attacked over the network.
Am I affected by CVE-2026-32230?: Check whether you run uptime-kuma (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

uptime-kuma (npm): upgrade to 2.2.0 or later
```
npm install uptime-kuma@2.2.0
```

Technical details

The GET /api/badge/:id/ping/:duration endpoint in server/routers/api-router.js fails to validate that the requested monitor belongs to a public status page, unlike five other badge endpoints which correctly enforce an AND public = 1 check in their SQL queries. The vulnerable endpoint directly calls UptimeCalculator.getUptimeCalculator() with an attacker-supplied monitor ID without authorization verification. Any unauthenticated user on the network can enumerate monitor IDs and extract average response time data, allowing reconnaissance of internal monitored systems. The vulnerability was introduced in version 2.0.0 and patched in version 2.2.0 by adding the same public monitor authorization check used by other badge endpoints.

Affected products

Uptime Kuma Uptime Kuma 2.0.0 to 2.1.3

Identifiers

CVE-2026-32230
GHSA-c7hf-c5p5-5g6h

Timeline

2026-03-12: disclosed
2026-03-12: patched: Fixed in version 2.2.0

References

https://github.com/louislam/uptime-kuma/security/advisories/GHSA-c7hf-c5p5-5g6h

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.