CVE-2026-85055: twentyhq twenty · Information Exposure
Affects twentyhq twentySource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 2.22.0 soon.
Data as of 5 Nov 2026, 00:01 UTC
- 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.
- Patch
- Available – fixed in 2.22.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Sep 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 5 Nov 2026.
What to do
Upgrade twenty and twentyhq/twenty to 2.22.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 twentyhq version 2.22.0 or later, where this vulnerability is fixed. No other mitigations are indicated by the vendor advisory. Patch status is confirmed by the fix in version 2.22.0.
Description
Twenty is an open-source CRM (customer relationship management) platform. Prior to 2.22.0, field-level read permission is enforced on selected output fields but not on GraphQL or REST filter predicates. A workspace member or API key with permission to read an object but not a particular field can reference that denied field in direct filters, relation filters, or persisted view filters. The resulting totalCount and row presence reveal whether guesses match the real column, forming a boolean/count oracle that can reconstruct denied field values for records exposed by the principal's row-level policy. This issue is fixed in version 2.22.0.
References
- github.com/twentyhq/twenty/security/advisories/GHSA-v93q-4jcx-7p9m (opens in a new tab)
- github.com/twentyhq/twenty/pull/22873 (opens in a new tab)
- github.com/twentyhq/twenty/commit/a5108d512f754a937860bda5e0c2c40c7266e19e (opens in a new tab)
- github.com/twentyhq/twenty/releases/tag/twenty/v2.22.0 (opens in a new tab)