Twenty: Field-level read bypass

Answer in brief

CVE-2026-85055 records a High severity (CVSS 7.1) vulnerability in Twenty: Field-level read bypass. The current sources do not mark it as known exploited. The current feed maps twentyhq/twenty (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 22, 2026Updated Sep 22, 2026Source checked Sep 22, 2026First seen by HOL Sep 22, 2026Material review Sep 22, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.1
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps twentyhq/twenty (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
twentyhq/twentygeneric	<2.22.0	2.22.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for twentyhq/twenty.
Review the reported fix. Update twentyhq/twenty to 2.22.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 22, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.