Skip to main content
VulnerabilityPublished

CVE-2026-66749: sdelements lets-chat · NULL Pointer Dereference

Affects sdelements lets-chatSource CVE Database V5

0

Not known to be exploited · CVSS 7.1 High.

Data as of 28 Oct 2026, 05:11 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
sdelementslets-chatAffected
  • >=0.4.0 <=0.4.8
Fixed in–
GitHublets-chatpkg:github/lets-chatOther threatsAffected
  • >=0.4.0 <=0.4.8
Fixed in–

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

AI-suggested

Until a fix is available, restrict access to authenticated users and monitor for unusual GET /messages requests with crafted room parameters. Consider implementing application-level input validation to reject invalid room parameters that do not correspond to existing database documents. Avoid exposing the socket.io interface to untrusted users if possible.

Description

Let's Chat 0.4.0 through 0.4.8 contains a null dereference vulnerability that allows authenticated attackers to crash the server by supplying a valid 24-character hex string room parameter that matches no document in the database. Attackers can send a crafted GET /messages request causing an uncaught TypeError in an asynchronous Mongoose callback that terminates the Node.js server process, with the same defect reachable through multiple code paths including the socket.io interface.

References

Community reviews

Loading reviews…