CVE-2026-105763: twentyhq twenty · Insufficiently Protected Credentials
Affects twentyhq twentySource CVE Database V5
Not known to be exploited · CVSS 9.6 Critical : upgrade to 2.7.0 as a priority.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.7.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 5 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 18 Nov 2026.
What to do
Upgrade twenty and twentyhq/twenty to 2.7.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| twentyhqtwenty | Affected
| Fixed in
|
GitHubtwentyhq/twentypkg:github/twentyhq/twentyOther 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 to version 2.7.0 or later, where the issue is fixed. No other mitigations are indicated. Since this is not a cloud service, remediation depends on applying the official fix.
Description
Twenty is an open-source CRM platform with a vulnerability in versions from 1.20.10 up to but not including 2.7.0. The /metadata GraphQL connectedAccounts query exposed plaintext IMAP, SMTP, and CalDAV passwords of connected accounts to any workspace member due to insufficient access controls. This allowed unauthorized users to retrieve other members' external-service credentials. Workspaces using only Google and Microsoft OAuth were not affected. The issue is fixed in version 2.7.0.