CVE-2026-73069

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (51st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-56221 (ENISA EUVD)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

Twenty is an open-source CRM (customer relationship management) platform. Prior to 2.15.0, Twenty allowed a workspace administrator with the DATA_MODEL permission to supply settings.asExpression for the system TS_VECTOR field searchVector through PATCH /rest/metadata/fields/:id or the updateOneField GraphQL mutation, causing buildSqlColumnDefinition in packages/twenty-server/src/engine/twenty-orm/workspace-schema-manager/utils/build-sql-column-definition.util.ts to concatenate unescaped input into GENERATED ALWAYS AS (...) and execute arbitrary PostgreSQL statements as the application database user. This issue is fixed in version 2.15.0.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 11, 2026

Last Modified

October 24, 2026

Advisory Details (3)

Auto-updated Sep 15, 2026
Fix named in the CVE record. Sources: github_pr, github, github_commit.
GitHub advisoryMentions a patch (unverified)

SQL Injection in Twenty `searchVector` Field Settings Allows Arbitrary PostgreSQL Execution · Advisory · twentyhq/twenty · GitHub

https://github.com/twentyhq/twenty/security/advisories/GHSA-mm7j-q9q3-qqwj
GitHub pull request

Refactor search vector field

Fix merged in twentyhq/twenty PR #21947 on 2026-06-22 — awaiting tagged release

https://github.com/twentyhq/twenty/pull/21947
GitHub commit

commit 0b8368cd6c1a (twentyhq/twenty)

Fix landed in twentyhq/twenty commit 0b8368cd6c1a — awaiting tagged release

https://github.com/twentyhq/twenty/commit/0b8368cd6c1a47711bf52972800f162bde0bbab9

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 58× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 151 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 51 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-30 05:45 UTCEG score recompute
  2. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  3. 2026-10-29 07:28 UTCEG score recompute
  4. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  5. 2026-10-28 09:11 UTCEG score recompute
  6. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  7. 2026-10-27 10:21 UTCEG score recompute
  8. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  9. 2026-10-26 12:04 UTCEG score recompute
  10. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  11. 2026-10-25 14:06 UTCEG score recompute
  12. 2026-10-25 13:43 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  14. 2026-10-23 19:28 UTCEG score recompute
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  16. 2026-10-23 01:02 UTCEG score recompute
  17. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  18. 2026-10-22 02:19 UTCEG score recompute
  19. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  20. 2026-10-21 03:53 UTCEG score recompute
  21. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  22. 2026-10-20 05:35 UTCEG score recompute
  23. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  24. 2026-10-19 07:14 UTCEG score recompute
  25. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
Show 75 more
  1. 2026-10-18 03:15 UTCEG score recompute
  2. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  3. 2026-10-17 10:34 UTCEG score recompute
  4. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  5. 2026-10-16 12:13 UTCEG score recompute
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  7. 2026-10-15 13:48 UTCEG score recompute
  8. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  9. 2026-10-14 08:43 UTCEG score recompute
  10. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  11. 2026-10-13 04:02 UTCEG score recompute
  12. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  13. 2026-10-12 15:41 UTCEG score recompute
  14. 2026-10-11 19:26 UTCEG score recompute
  15. 2026-10-11 16:42 UTCEG score recompute
  16. 2026-10-11 14:02 UTCEG score recompute
  17. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  18. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  19. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  20. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  21. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  22. 2026-10-06 17:53 UTCEG score recompute
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  24. 2026-10-05 18:01 UTCEG score recompute
  25. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  26. 2026-10-05 07:40 UTCEG score recompute
  27. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  28. 2026-10-03 21:03 UTCEG score recompute
  29. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  30. 2026-10-02 22:26 UTCEG score recompute
  31. 2026-10-02 08:43 UTCEG score recompute
  32. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  33. 2026-09-30 22:18 UTCEG score recompute
  34. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  35. 2026-09-29 05:14 UTCEG score recompute
  36. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  37. 2026-09-27 16:55 UTCEG score recompute
  38. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  39. 2026-09-27 10:24 UTCEG score recompute
  40. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  41. 2026-09-25 03:55 UTCEG score recompute
  42. 2026-09-23 21:03 UTCEG score recompute
  43. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  44. 2026-09-22 21:13 UTCEG score recompute
  45. 2026-09-21 21:11 UTCEG score recompute
  46. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  47. 2026-09-21 00:53 UTCEG score recompute
  48. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  49. 2026-09-19 17:16 UTCEG score recompute
  50. 2026-09-18 23:19 UTCEG score recompute
  51. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  52. 2026-09-18 00:47 UTCEG score recompute
  53. 2026-09-17 00:34 UTCEG score recompute
  54. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  55. 2026-09-16 06:33 UTCEG score recompute
  56. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  57. 2026-09-15 07:35 UTCEG score recompute
  58. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  59. 2026-09-13 20:08 UTCEG score recompute
  60. 2026-09-12 17:34 UTCEG score recompute
  61. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  62. 2026-09-11 18:28 UTCEG score recompute
  63. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  64. 2026-09-11 14:04 UTCEG score recompute
  65. 2026-09-10 12:34 UTCEG score recompute
  66. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  67. 2026-09-09 05:41 UTCEG score recompute
  68. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  69. 2026-09-07 17:01 UTCEG score recompute
  70. 2026-09-06 18:11 UTCEG score recompute
  71. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  72. 2026-09-05 19:45 UTCEG score recompute
  73. 2026-09-04 17:05 UTCEG score recompute
  74. 2026-09-04 08:18 UTCEG score recompute
  75. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.4% · 28th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73069?
CVE-2026-73069 is a critical-severity vulnerability; its CVE record was published on August 11, 2026. Twenty is an open-source CRM (customer relationship management) platform. Prior to 2.15.0, Twenty allowed a workspace administrator with the DATAMODEL permission to supply settings.asExpression for the system TSVECTOR field searchVector through PATCH /rest/metadata/fields/:id or the updateOneField…
When was the CVE record for CVE-2026-73069 published?
The CVE record for CVE-2026-73069 was published on August 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-73069 actively exploited?
CVE-2026-73069 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73069?
CVE-2026-73069 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73069?
The CVE record for CVE-2026-73069 names the fix: "This issue is fixed in version 2.15.0."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-73069

Explore →

Is Your Infrastructure Affected by CVE-2026-73069?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs