Quick answers
- Is CVE-2026-85055 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85055 being exploited in the wild.
- How severe is CVE-2026-85055?
- Informational severity, published 22 September 2026.
- Which products and versions are affected?
- Twenty before 2.22.0.
- Is there a fix for CVE-2026-85055?
- A patch was published on 2026-07-16: Fix released in version 2.22.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-85055 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-85055?
- Check whether you run Twenty at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Field-level read permissions in Twenty are enforced on output fields in GraphQL and REST responses, but not on filter predicates in direct filters, relation filters, or persisted view filters. An authenticated user can submit filter conditions on restricted fields and use the resulting totalCount or row presence as a boolean oracle to enumerate denied field values. This affects both direct field filtering and cross-relation filtering through related objects.
Affected products
- Twenty Twenty before 2.22.0
Timeline
- 2026-09-22: disclosed
- 2026-07-16: patched: Fix released in version 2.22.0