CVE-2026-85055: high-severity vulnerability in twentyhq twenty
Twenty: Field-level read bypass
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.1epss 0.4%
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Affected products
twentyhq · twentyRelated CVEs — twentyhq twenty
In the same product, most dangerous first.
CVE-2026-73069CRITICALTwenty: SQL Injection in the `searchVector` Field Settings Allows Arbitrary PostgreSQL ExecutionEPSS 0.7%CVE-2026-46624CRITICALTwenty: SQL Injection via the timeZone fieldEPSS 0.5%CVE-2026-92771HIGHTwenty before 2.35.0 Permission Bypass via groupBy-with-records QueryEPSS 0.4%CVE-2026-82274MEDIUMTwenty Open Redirect via OAuth Propagator CallbackEPSS 0.4%CVE-2026-35451MEDIUMTwenty: Stored XSS via BlockNote FileBlockEPSS 0.3%CVE-2026-105763CRITICALTwenty: Plaintext IMAP/SMTP/CalDAV password disclosure to any workspace member via /metadata GraphQLEPSS 0.3%