CVE-2026-102669: Joyland.ai · Improper Validation of Certificate with Host Mismatch
Affects Joyland.aiSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Oct 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 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| JoylandJoyland.ai | Affected
| Fixed in– |
AI-suggested
Since this is not a cloud service, remediation depends on the vendor releasing an update that properly validates hostnames in TLS certificates. Users should monitor vendor advisories for updates. Until a fix is available, avoid using Joyland.ai in untrusted network environments where interception is possible.
Description
Joyland.ai suffers from improper validation of TLS certificates, specifically failing to verify hostnames. This flaw allows a malicious host to connect or intercept chat messages by presenting a certificate with a mismatched hostname. The vulnerability affects all versions of Joyland.ai. It has a medium severity with a CVSS score of 5.3. No official patch or remediation guidance is currently available from the vendor.