dbcve.org
TwentyApplication

CVE-2026-46624

CRITICAL · 9.9 CVSS v3.1 Published 2026-05-26
Fix available
A fix is available. Upgrade to 1.16.7 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Twenty is an open source CRM. From 1.7.7 through 1.16.7, a critical Remote Code Execution (RCE) vulnerability exists in Twenty CRM via a chained SQL Injection and PostgreSQL COPY TO PROGRAM attack. If Postgres user is a super user then any authenticated user can execute arbitrary OS commands on the database server by injecting SQL through the unsanitized timeZone parameter in the REST API groupBy endpoint. The timeZone field within the group_by query parameter is directly interpolated into a raw SQL expression using JavaScript template literals without any parameterization, validation, or escaping. This affects engine/api/graphql/graphql-query-runner/group-by/resolvers/utils/get-group-by-expression.util.ts.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A critical SQL injection vulnerability in Twenty CRM allows authenticated users to execute arbitrary OS commands via the groupBy endpoint. The timeZone parameter in the group_by query is directly interpolated into raw SQL using JavaScript template literals without sanitization, combined with a PostgreSQL COPY TO PROGRAM attack when the database user has superuser privileges.

MitigationImmediately upgrade to a version beyond 1.16.7, or apply input validation and parameterized queries to replace template literal SQL interpolation in get-group-by-expression.util.ts. Additionally, ensure the PostgreSQL user for Twenty CRM is not a superuser.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TwentyApplication
Affected:>= 1.7.7, < 1.16.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Twenty CRM installed version
    Run the command: docker ps --format '{{.Names}}' | xargs -I {} docker exec {} cat package.json 2>/dev/null | grep '"version"' or check your deployment manifests/config files for the installed version tag
    Affected if Version is >= 1.7.7 and < 1.16.7
  2. Verify REST API is enabled
    Confirm Twenty CRM REST API endpoints are accessible in your environment; check server configuration for API route availability
    Affected if REST API is exposed and accessible to authenticated users
  3. Check PostgreSQL database user privileges
    Connect to the Twenty CRM database as the application database user and run: SELECT rolname, rolsuper FROM pg_roles WHERE rolname = CURRENT_USER; or check your database connection configuration for the user privileges
    Affected if The database user has superuser privileges (rolsuper = true)
  4. Confirm groupBy endpoint exists
    Review Twenty CRM source code in server/src/workspace/workspace-query-builder folder for the groupBy function that uses the timeZone parameter, or test access to /api/groupBy endpoints if API documentation is available
    Affected if The groupBy endpoint functionality is present in the installation

You are affected if Twenty CRM version is between 1.7.7 and 1.16.7, the REST API is accessible to authenticated users, and your PostgreSQL database user has superuser privileges, allowing SQL injection via the timeZone parameter to escalate to OS command execution.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.16.7 or later
Fixed in 1.16.7
Interim mitigation

Immediately upgrade to a version beyond 1.16.7, or apply input validation and parameterized queries to replace template literal SQL interpolation in get-group-by-expression.util.ts. Additionally, ensure the PostgreSQL user for Twenty CRM is not a superuser.

Recommended fix High confidence

1.16.7 or later

  1. Backup your Twenty CRM database and application data before proceeding
  2. Check your current Twenty version (typically in package.json or system settings)
  3. Upgrade Twenty CRM to version 1.16.7 or later using your deployment method (e.g., Docker, npm, or relevant package manager)
  4. After upgrade, verify the timeZone parameter in groupBy endpoint is now properly parameterized/validated
  5. Restart all application services to ensure the patched code is loaded
  6. Verify the fix by testing the groupBy endpoint with various timeZone inputs - the raw SQL should no longer accept direct template literal interpolation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Twenty Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46624 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46624 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data