CVE-2026-71862: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in bluewave-labs Checkmate
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. From 3.3.0 until 3.9.2, enabling the global showURL setting causes the unauthenticated GET /api/v1/status-page/:url endpoint to return complete monitor objects from server/src/controllers/statusPageController.ts. The response includes the secret field used by HttpProvider.ts as an HTTP Authorization credential, even though BaseStatusPage.tsx does not display that value, allowing visitors to extract credentials from the JSON response and use them against monitored services. This issue is fixed in version 3.9.2.
CVSS v3.1
Score 7.5high
Affected software
bluewave-labs
Checkmate
pkg:github/bluewave-labs/CheckmateRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In Checkmate, an open-source server monitoring tool, versions from 3.3.0 up to but not including 3.9.2 have a security flaw triggered by enabling the global showURL setting. This flaw causes the unauthenticated GET /api/v1/status-page/:url endpoint to return full monitor objects containing a secret field used as an HTTP Authorization credential. Although the frontend does not display this secret, it is present in the JSON response, enabling unauthorized users to obtain sensitive credentials and potentially misuse them against monitored services. The vulnerability is identified as CWE-200 (Exposure of Sensitive Information) and CWE-522 (Insufficiently Protected Credentials). The vulnerability has a CVSS 3.1 score of 7.5 (high severity) and is fixed in version 3.9.2.
Potential Impact
Unauthorized actors can retrieve sensitive HTTP Authorization credentials from the unauthenticated API endpoint when the showURL setting is enabled. This exposure can lead to misuse of these credentials against monitored services, potentially compromising the confidentiality of those services. There is no indication of impact on integrity or availability. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade Checkmate to version 3.9.2 or later, where this vulnerability is fixed. Until then, avoid enabling the global showURL setting to prevent exposure of sensitive credentials via the unauthenticated API endpoint.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-07T18:26:53.524Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a8893f9acd9273b4983fd51
Added to database: 08/21/2026, 18:07:53 UTC
Last enriched: 08/21/2026, 19:37:14 UTC
Last updated: 10/05/2026, 18:48:22 UTC
Views: 71
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.