Skip to main content
VulnerabilityPublished Updated

CVE-2026-55241: bluewave-labs Checkmate · Uncontrolled Resource Consumption

Affects bluewave-labs CheckmateSource CVE Database V5

0
Compare

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

Data as of 18 Nov 2026, 20:25 UTC

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

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 18 Nov 2026.

What to do

Upgrade Checkmate and bluewave-labs/Checkmate to 3.9.1.

Affected software

ProductAffectedFixed in
bluewave-labsCheckmateAffected
  • <3.9.1
Fixed in
  • 3.9.1
GitHubbluewave-labs/Checkmatepkg:github/bluewave-labs/CheckmateOther threatsAffected
  • <3.9.1
Fixed in
  • 3.9.1

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.1 or later, where the issue is fixed by adding file size, count, and MIME type limits before buffering uploads. No other mitigations are specified. Patch status is confirmed fixed in 3.9.1.

Description

CVE-2026-55241 is a high-severity vulnerability in bluewave-labs Checkmate prior to version 3.9.1. It involves uncontrolled resource consumption via the public POST /api/v1/auth/register endpoint, which processes multipart profile image uploads without limits on file size, count, or MIME type. An unauthenticated attacker can submit concurrent oversized files that are buffered in memory before registration validation, leading to memory exhaustion and potential backend crashes or destabilization. This issue is fixed in version 3.9.1.

References

Community reviews

Loading reviews…