CVE-2026-71862: Checkmate: Sensitive Bearer Token Exposure via Public Status Pages When showURL Setting is Enabled

Published Aug 21, 2026
·
Updated

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.

Affected Software

1 affected component
checkmate>=3.3.0<=3.9.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Checkmate to a version that resolves this vulnerability.

    Fixed in 3.9.2

Event History

Aug 21, 2026
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

Checkmate deployments from 3.3.0 through 3.9.2 are exposed when the global showURL setting is enabled. The affected status-page API endpoint is unauthenticated, so public visitors can retrieve the data.

2

What does an attacker need to exploit this issue?

An attacker only needs network access to the public status-page endpoint and its URL. No account, privileges, or user interaction are required.

3

What can be exposed and how could it be used?

The endpoint returns complete monitor objects, including the secret field used by HttpProvider.ts as an HTTP Authorization credential. An attacker can extract that credential from the JSON response and use it against the monitored service.

4

What should be done if an immediate upgrade is not possible?

Disable the global showURL setting to prevent the affected endpoint behavior. Treat credentials configured in monitor secret fields as potentially exposed and rotate them where appropriate.

5

What version fixes the issue?

The issue is fixed in Checkmate version 3.9.2.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203