CVE-2026-70656: bluewave-labs Checkmate · ReDoS
Affects bluewave-labs CheckmateSource CVE Database V5
Not known to be exploited · CVSS 4.9 Medium : upgrade to 3.9.2 when convenient.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 48% 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:H/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 18 Nov 2026.
What to do
Upgrade Checkmate and bluewave-labs/Checkmate to 3.9.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| bluewave-labsCheckmate | Affected
| Fixed in
|
GitHubbluewave-labs/Checkmatepkg:github/bluewave-labs/CheckmateOther threats | Affected
| Fixed in
|
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. No other official remediation or temporary workaround is documented. Patch status is not explicitly stated but the fix is included in version 3.9.2.
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.5.1 until 3.9.2, an authenticated admin or superadmin can set matchMethod to regex and place a malicious expression in the expectedValue field for advanced HTTP monitor matching. server/src/api/validation/monitorValidation.ts accepts the expression, and server/src/service/network/AdvancedMatcher.ts synchronously evaluates it against an attacker-controlled HTTP response body on the Node.js main event loop without a timeout or worker isolation, allowing catastrophic backtracking to freeze API endpoints, monitor checks, and WebSocket connections for all users. This issue is fixed in version 3.9.2.
References
- github.com/bluewave-labs/Checkmate/security/advisories/GHSA-4c6j-p2cv-wf56 (opens in a new tab)
- github.com/bluewave-labs/Checkmate/commit/0df71d6356c87c747e0b796b0c34e33f2a5203fa (opens in a new tab)
- github.com/bluewave-labs/Checkmate/commit/adba25269c455878bf8065bc28cfe5d74e58692f (opens in a new tab)
- github.com/bluewave-labs/Checkmate/commit/d5ec2936ad77ab773529057b442a6eb55dd578eb (opens in a new tab)
- github.com/bluewave-labs/Checkmate/releases/tag/v3.9.2 (opens in a new tab)