CVE-2026-72588

bluewave-labs Checkmate - User Enumeration via Differential HTTP Response in Password Recovery

Published Aug 10, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

A user enumeration vulnerability in Checkmate allows remote attackers to determine whether a given email address is registered by exploiting a difference in HTTP status codes returned from the /api/v1/auth/recovery/request endpoint. The endpoint replies with HTTP 200 when the email exists and a different code when it does not, exposing legitimate account information and aiding targeted phishing or credential‑stuffing attacks. This weakness corresponds to CWE‑204 (Information Exposure through Indirect Detection).

Affected Systems

The affected product is bluewave‑labs Checkmate, and the vulnerability exists in all releases up to and including version 2.1.0. Deployments using any of these releases are susceptible, and no vendor‑supplied workaround is publicly documented.

Risk and Exploitability

The CVSS score of 5.3 places the vulnerability in the medium severity range. EPSS data is not available, and it is not currently listed in the CISA KEV catalog, indicating a moderate potential for exploitation. An unauthenticated attacker with network access can exploit the flaw by submitting POST requests to the password‑recovery API and observing status codes; no privileged permissions are required. While the attack vector is limited to the recovery endpoint, the ability to enumerate accounts can enable subsequent targeted attacks.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Checkmate to a version newer than 2.1.0 that contains the fix for the enumeration flaw.
  • As an interim measure, implement rate limiting or temporarily disable the /api/v1/auth/recovery/request endpoint to reduce enumeration opportunities.
  • Restrict external network access to the authentication services using firewall rules or network segmentation to limit the attack surface.
  • Continuously monitor logs for repeated requests to the recovery endpoint and investigate anomalies to detect enumeration attempts.

Generated by OpenCVE AI on August 10, 2026 at 12:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
References
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Bluewave-labs
Bluewave-labs checkmate
Vendors & Products Bluewave-labs
Bluewave-labs checkmate
Type Values Removed Values Added
Description 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.
Title bluewave-labs Checkmate - User Enumeration via Differential HTTP Response in Password Recovery
Weaknesses CWE-204
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'}

Weaknesses
  • CWE-204

    Observable Response Discrepancy

Sources

Status
PUBLISHED
Assigner
TuranSec
Published
Updated
Aug 10, 2026, 1:22 PM
Reserved
Aug 10, 2026, 10:32 AM
Status
Deferred
Published
Aug 10, 2026, 11:17 AM
Modified
Oct 24, 2026, 3:10 PM