# 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

> Unauthenticated attackers can access private monitor ping data due to missing authorization checks on the ping badge endpoint.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Mar 2026
- **Updated:** 13 Mar 2026
- **Also known as:** GHSA-c7hf-c5p5-5g6h

## What is CVE-2026-32230?

CVE-2026-32230 is a medium-severity missing authorization vulnerability in louislam uptime-kuma, published on 12 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-32230?

2 open source packages ship an affected version, including uptime-kuma. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `uptime-kuma` | npm | From 2.0.0 | 2.2.0 |
| `uptime-kuma` | npm | From 2.0.0 | 2.2.0 |

Products: Uptime.kuma Uptime Kuma.

## How do I fix CVE-2026-32230?

Upgrade uptime-kuma to 2.2.0 or later.

## Is CVE-2026-32230 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32230 exists.

Public exploit code:

- Uptime-Kuma < v1.23.0 - Improper Access Control (nuclei): http/cves/2026/CVE-2026-32230.yaml

## Other vulnerabilities in louislam uptime-kuma

- [CVE-2023-44400](https://insights.sbomify.com/CVE-2023-44400/): Uptime Kuma has Persistentent User Sessions (medium 6.7)
- [CVE-2026-33130](https://insights.sbomify.com/CVE-2026-33130/): Uptime Kuma: SSTI in Notification Templates Allows Arbitrary File Read (Incomplete Fix for GHSA-vffh-c9pq-4crh) (medium 6.5)
- [CVE-2023-49276](https://insights.sbomify.com/CVE-2023-49276/): Attribute Injection leading to XSS(Cross-Site-Scripting) in uptime-kuma (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32230 and fix it if it is affected.

What it is: CVE-2026-32230 is a medium-severity missing authorization vulnerability in louislam uptime-kuma, published on 12 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32230 exists.

Affected packages and fixed versions:
- uptime-kuma (npm): affected from 2.0.0; fixed in 2.2.0
- uptime-kuma (npm): affected from 2.0.0; fixed in 2.2.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32230/ (Markdown: https://insights.sbomify.com/CVE-2026-32230/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32230
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32230
- OSV: https://osv.dev/vulnerability/CVE-2026-32230

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32230/
Summaries are generated and may contain mistakes; the official description above is the record.