VulnerabilityPublished 7 Mar 2026Updated 10 Mar 2026

CVE-2026-30829: bluewave-labs Checkmate · Information Exposure

Affects bluewave-labs CheckmateSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.4.0 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

5.3Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.4.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 7 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
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: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 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 Checkmate and bluewave-labs/Checkmate to 3.4.0.

Affected software

Product	Affected	Fixed in
bluewave-labsCheckmate	Affected <3.4.0	Fixed in 3.4.0
GitHubbluewave-labs/Checkmate`pkg:github/bluewave-labs/Checkmate`Other threats	Affected <3.4.0	Fixed in 3.4.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 bluewave-labs Checkmate versions prior to 3.4.0 should upgrade immediately to version 3.4.0 or later, where this vulnerability is patched. Until upgrading, administrators should restrict network access to the Checkmate API endpoints, especially the /api/v1/status-page/:url endpoint, using firewall rules or network segmentation to limit exposure to trusted users only. Implementing authentication and authorization controls at the network or application proxy level can help prevent unauthorized API access. Review and minimize the amount of sensitive information displayed on status pages, particularly unpublished ones, to reduce potential data exposure. Regularly audit API access logs for suspicious or unauthorized requests targeting status pages. Additionally, consider deploying web application firewalls (WAFs) with rules to detect and block unauthenticated access attempts to sensitive API endpoints. Maintain an up-to-date inventory of Checkmate deployments and monitor vendor advisories for future security updates.

Description

Checkmate is an open-source, self-hosted tool designed to track and monitor server hardware, uptime, response times, and incidents in real-time with beautiful visualizations. Prior to version 3.4.0, an unauthenticated information disclosure vulnerability exists in the GET /api/v1/status-page/:url endpoint. The endpoint does not enforce authentication or verify whether a status page is published before returning full status page details. As a result, unpublished status pages and their associated internal data are accessible to any unauthenticated user via direct API requests. This issue has been patched in version 3.4.0.

Impact

The primary impact of this vulnerability is unauthorized disclosure of sensitive internal monitoring data, which could include server status, uptime metrics, incident reports, and other operational details. Such exposure can aid attackers in reconnaissance, allowing them to identify potential targets, understand infrastructure weaknesses, or plan further attacks. While the vulnerability does not allow modification or disruption of services, the loss of confidentiality can undermine organizational security posture and privacy. Organizations relying on Checkmate for critical infrastructure monitoring may face increased risk of targeted attacks if this information is leaked. The impact is heightened in environments where status pages contain sensitive or proprietary operational data. Since exploitation requires no authentication or user interaction, the vulnerability can be exploited remotely and easily by any attacker aware of the API endpoint. However, the lack of known active exploits suggests limited current exploitation. Prompt patching is essential to mitigate potential future risks.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/bluewave-labs/Checkmate/security/advisories/GHSA-57xf-wg6w-fjrr (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Mar 2026, 19:34 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats