Skip to main content

Checkmate EUVDEUVD-2026-55218

| CVE-2026-72588 MEDIUM
Observable Response Discrepancy (CWE-204)
2026-08-10 TuranSec GHSA-cjr5-m69m-f39c
5.3
CVSS 3.1 · Vendor: TuranSec
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify Checkmate instance URL
  2. Delivery
    Send POST /api/v1/auth/recovery/request with candidate emails
  3. Exploit
    Observe HTTP 200 vs. non-200 responses
  4. Execution
    Map valid registered accounts
  5. Impact
    Target 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.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

Checkmate 0 <2.1.0

Affected Packages

euvd checkmate fix: 2.1.0

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

Vendor (TuranSec) PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
vuln.today AI 5.3 MEDIUM

Network-accessible unauthenticated endpoint; low confidentiality impact limited to account existence; no integrity or availability impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (TuranSec).

CVSS VectorVendor: TuranSec

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

Lifecycle Timeline

1
Patch available
Aug 10, 2026 - 12:17 EUVD

DescriptionCVE.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

EPSS Score
0.3%
Top 83% exploitable
Prevalence
Low
niche open-source monitoring tool, limited enterprise footprint
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy