Quick answers
- Is CVE-2026-73069 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-73069 being exploited in the wild.
- How severe is CVE-2026-73069?
- Critical severity, with a CVSS score of 9.1, published 11 August 2026.
- Which products and versions are affected?
- Twenty prior to 2.15.0.
- Is there a fix for CVE-2026-73069?
- A patch was published on 2026-06-22: Fix released in version 2.15.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-73069 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-73069?
- 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
This is a SQL injection vulnerability in the search vector field configuration mechanism. The vulnerable code path exists in buildSqlColumnDefinition within the workspace schema manager, where user-supplied settings.asExpression values for the TS_VECTOR searchVector field are concatenated directly into SQL GENERATED ALWAYS AS clauses without proper escaping or validation. An authenticated workspace administrator with the DATA_MODEL permission can exploit this by sending a PATCH request to /rest/metadata/fields/:id or using the updateOneField GraphQL mutation to supply malicious PostgreSQL expressions. The application executes these unescaped inputs as the database user, allowing arbitrary SQL statement execution. The vulnerability was patched in version 2.15.0 by implementing proper input validation for search vector field expressions.
Affected products
- Twenty Twenty prior to 2.15.0
Timeline
- 2026-08-11: disclosed
- 2026-06-22: patched: Fix released in version 2.15.0