VulnerabilityPublished 12 Mar 2026

CVE-2026-32230: louislam uptime-kuma · Missing Authorization

Affects louislam uptime-kumaSource CVE Database V5

Exposed hosts seen by OffSeq Mirage · public detection template (Nuclei) · CVSS 5.3 Medium : upgrade to 2.2.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.2.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Mar 2026
Detectable: evidence found.
nuclei template: Uptime-Kuma < v1.23.0 - Improper Access Control
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: evidence found.
1 exposed host found; no attack traffic recorded

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), OffSeq Mirage (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade uptime-kuma and louislam/uptime-kuma to 2.2.0.

Affected software

Product	Affected	Fixed in
louislamuptime-kuma	Affected >=2.0.0 <2.2.0	Fixed in 2.2.0
GitHublouislam/uptime-kuma`pkg:github/louislam/uptime-kuma`Other threats	Affected <2.2.0	Fixed in 2.2.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations using Uptime Kuma versions 2.0.0 to 2.1.3 should upgrade immediately to version 2.2.0 or later, where the authorization check on the /api/badge/:id/ping/:duration? endpoint is properly enforced. Until upgrading is possible, administrators should consider restricting network access to the Uptime Kuma server to trusted internal networks only, preventing unauthenticated external access to the API endpoints. Additionally, implementing web application firewalls (WAFs) with rules to detect and block suspicious API requests targeting badge endpoints can reduce exposure. Monitoring API logs for unusual access patterns to badge endpoints may help detect exploitation attempts. Reviewing and minimizing the number of private monitors exposed via badges and ensuring that sensitive monitoring data is not publicly accessible can further reduce risk. Finally, organizations should maintain an inventory of affected software versions and apply security patches promptly to prevent exploitation.

Description

CVE-2026-32230 is a medium severity vulnerability in Uptime Kuma versions 2.0.0 through 2.1.3 where the GET /api/badge/:id/ping/:duration? endpoint fails to verify authorization properly. This flaw allows unauthenticated users to access average ping/response time data for private monitors, bypassing the intended access control that restricts such data to public monitors only. The vulnerability arises from missing authorization checks on this specific endpoint, while other badge endpoints correctly enforce public group verification. Exploitation requires no authentication or user interaction and can lead to unauthorized disclosure of monitoring data. The issue is fixed in version 2.

Impact

The primary impact of this vulnerability is unauthorized disclosure of monitoring data related to private monitors. Organizations relying on Uptime Kuma for internal service monitoring could inadvertently expose sensitive operational metrics such as average ping and response times to unauthenticated external actors. This information could aid attackers in reconnaissance activities, enabling them to identify critical internal services, assess their responsiveness, and potentially plan targeted attacks. While the vulnerability does not allow modification or disruption of services, the confidentiality breach could undermine organizational security postures and privacy requirements. Since exploitation requires no authentication and can be performed remotely, the risk of data leakage is significant for any organization running affected versions of Uptime Kuma, especially those monitoring sensitive or critical infrastructure. The absence of known exploits reduces immediate risk but does not eliminate the threat, as attackers could develop exploits given the public disclosure.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Mar 2026, 02:34 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats