Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify Checkmate instance URL
-
DeliverySend POST /api/v1/auth/recovery/request with candidate emails
-
ExploitObserve HTTP 200 vs. non-200 responses
-
ExecutionMap valid registered accounts
-
ImpactTarget accounts for phishing or credential stuffing
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V6 - Authentication Response uniformity
|
| Exploitation Conditions | No special conditions are required for exploitation beyond network access to the Checkmate web application. The CVSS vector confirms unauthenticated (PR:N) network (AV:N) exploitation with low complexity (AC:L) and no user interaction (UI:N). The password recovery endpoint is intentionally public-facing. Exploitation is limited to information disclosure - specifically, confirming email address registration status - and does not grant authentication or data access. Exploitation is constrained only by rate-limiting controls if present, and is not platform- or configuration-specific. |
| Impact | The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N scores 5.3 (Medium), accurately reflecting the limited confidentiality impact - an attacker learns only account existence, not credentials or data. EPSS data was not provided in the intelligence package, limiting probabilistic exploitation forecasting. There is no CISA KEV listing and no confirmed public exploit code, placing exploitation status at the lowest risk tier. However, the attack complexity is genuinely low: the endpoint is network-accessible, requires no authentication, and the enumeration signal (HTTP 200 vs. other) is unambiguous and scriptable. Even a small deployment - say, a mid-sized municipal IT team in opole operating a self-hosted Checkmate instance - could have its full user email list harvested silently with a simple script, enabling targeted phishing campaigns as a follow-on. The primary real-world risk is account pre-targeting for credential stuffing or spear phishing, not direct system compromise. SSVC signals: exploitation status unproven, attack is automatable, technical impact is partial - overall a low-to-medium operational priority unless the Checkmate instance hosts sensitive infrastructure accounts. |
| Exploit ScenarioDerived | An unauthenticated attacker sends automated POST requests to /api/v1/auth/recovery/request with a wordlist of candidate email addresses. By observing HTTP 200 versus non-200 responses, the attacker silently builds a list of valid registered accounts in minutes. That account list is then used as a target set for credential stuffing against the Checkmate login endpoint or for crafting convincing phishing emails. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 10, 2026
User enumeration via observable response discrepancy in Checkmate through version 2.1.0 exposes whether any given email address is registered on the platform. The password recovery endpoint POST /api/v1/auth/recovery/request returns HTTP 200 for known accounts and a distinct status code for unknown ones, allowing unauthenticated remote attackers to silently map valid user accounts. No public exploit or CISA KEV listing exists at time of analysis, but exploitation requires no authentication and is trivially automatable.
RemediationAI
Upstream fix availability is not independently confirmed - the sole reference is the GitHub repository at https://github.com/bluewave-labs/Checkmate, and no tagged patched release version was provided in the intelligence data. Operators should monitor that repository for a fix and upgrade immediately upon release. As a compensating control prior to patching, the recovery endpoint should be modified to return a uniform HTTP 200 response regardless of whether the submitted email is registered, with any real error communicated only via a generic message (e.g., 'If that address is registered, you will receive an email'). Rate-limiting and CAPTCHA on the recovery endpoint will raise enumeration cost but will not eliminate the discrepancy-based signal. Blocking external access to the recovery endpoint entirely is the most effective interim control if the user base is internal-only, at the cost of disabling self-service password recovery for remote users.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Checkmate is an open-source uptime and infrastructure monitoring platform maintained by bluewave-labs (CPE: cpe:2.3:a:bluewave-labs:checkmate:*:*:*:*:*:*:*:*). The vulnerability is classified as CWE-204: Observable Response Discrepancy, a root cause where an application reveals whether a resource (here, a user account) exists by returning meaningfully different responses - in this case, different HTTP status codes - to otherwise identical requests. The affected endpoint is the account recovery initiation route, a common attack surface for enumeration because it must query the user store but is intentionally unauthenticated. Differential HTTP response codes (rather than a uniform response regardless of account existence) is the specific implementation flaw.
Know when Checkmate gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Network-accessible unauthenticated endpoint; low confidentiality impact limited to account existence; no integrity or availability impact.
Primary rating from Vendor (TuranSec).
CVSS VectorVendor: TuranSec
Lifecycle Timeline
1DescriptionCVE.org
A user enumeration vulnerability in bluewave-labs/Checkmate through 2.1.0 allows an unauthenticated remote attacker to determine whether a given email address is registered. The POST /api/v1/auth/recovery/request endpoint returns HTTP 200 for registered email addresses and a different status code for unregistered ones, enabling attackers to enumerate valid user accounts.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Checkmate versions prior to 3.4.0 allow unauthenticated attackers to retrieve unpublished status pages and internal moni
A mass assignment vulnerability in Checkmate's user profile update endpoint allows any authenticated user to escalate th
Remote memory exhaustion in Bluewave Labs Checkmate prior to version 3.9.1 allows unauthenticated network attackers to c
Credential leakage in Bluewave Labs Checkmate versions 3.3.0 through 3.9.1 exposes HTTP Authorization secrets to unauthe
Missing role-guard middleware on three API route groups in Checkmate through v3.11.0 allows any authenticated low-privil
ReDoS (catastrophic regex backtracking) in Checkmate monitoring platform versions 3.5.1 through 3.9.1 allows an authenti
EUVD-2026-55218
GHSA-cjr5-m69m-f39c
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB