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
Share

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

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

Lifecycle Timeline

2
Patch available
Aug 10, 2026 - 12:17 EUVD
Analysis Generated
Aug 10, 2026 - 11:31 vuln.today

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.

AnalysisAI

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

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Identify Checkmate instance URL
Delivery
Send POST /api/v1/auth/recovery/request with candidate emails
Exploit
Observe HTTP 200 vs. non-200 responses
Execution
Map valid registered accounts
Impact
Target accounts for phishing or credential stuffing

Vulnerability AssessmentAI

Exploitation No special conditions are required for exploitation beyond network access to the Checkmate web application. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment 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. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario 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. …
Remediation 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. … Detailed patch versions, workarounds, and compensating controls in full report.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

EUVD-2026-55218 vulnerability details – vuln.today

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