Skip to main content
VulnerabilityPublished

CVE-2026-71862: bluewave-labs Checkmate · Information Exposure

Affects bluewave-labs CheckmateSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 3.9.2 soon.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.9.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade Checkmate and bluewave-labs/Checkmate to 3.9.2.

Affected software

ProductAffectedFixed in
bluewave-labsCheckmateAffected
  • >=3.3.0 <3.9.2
Fixed in
  • 3.9.2
GitHubbluewave-labs/Checkmatepkg:github/bluewave-labs/CheckmateOther threatsAffected
  • <3.9.2 >=3.3.0
Fixed in
  • 3.9.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

References

Community reviews

Loading reviews…