# CVE-2026-92771: Twenty before 2.35.0 Permission Bypass via groupBy-with-records Query

> Authenticated users can bypass field-level permission checks to retrieve restricted data via the groupBy GraphQL resolver.

- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-7q37-3m9h-f5mp

## What is CVE-2026-92771?

CVE-2026-92771 is a high-severity missing authorization vulnerability in twentyhq twenty, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Twenty before 2.35.0 fails to validate field and row permissions in the groupBy-with-records GraphQL resolver, allowing authenticated users to bypass permission checks. Attackers with canReadObjectRecords permission but canReadFieldValue false can retrieve restricted field values through the groupBy resolver that would normally be denied.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-92771?


## How do I fix CVE-2026-92771?

No fix has been published for CVE-2026-92771 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92771 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92771 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92771 and fix it if it is affected.

What it is: CVE-2026-92771 is a high-severity missing authorization vulnerability in twentyhq twenty, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92771 exists.

Affected product: twentyhq twenty. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92771/ (Markdown: https://insights.sbomify.com/CVE-2026-92771/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92771
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92771
- OSV: https://osv.dev/vulnerability/CVE-2026-92771

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92771/
Summaries are generated and may contain mistakes; the official description above is the record.