CVE-2026-55583

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (13th 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-39051 (ENISA EUVD)Source: ENISA EUVD

7.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.2%CVSS: 7.6Exploit: 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.9.0, Twenty was vulnerable to a cross-workspace insecure direct object reference (IDOR) in the AI agent monitor's AgentTurnResolver, in packages/twenty-server/src/engine/metadata-modules/ai/ai-agent-monitor/reso lvers/agent-turn.resolver.ts. The agentTurns(agentId) query and the evaluateAgentTurn(turnId) mutation looked up rows by agentId or id only; although AgentTurnEntity has a workspaceId column, it was not included in the WHERE clause, and the class-level guards only checked that the caller was authenticated in some workspace rather than that the requested object belonged to it, with the same flaw present in agent-turn-grader.service.ts. As a result, any authenticated user with the AI settings flag, a workspace owner by default, could target any other workspace on the same instance given the victim's agentId or turnId: agentTurns returned the victim's full chat history including message parts such as raw chat text, tool calls, and tool outputs, while evaluateAgentTurn inserted an agentTurnEvaluation row with the victim's workspaceId and fed the victim's turn into the default LLM. The agentId and turnId are non-guessable UUIDs but are exposed in the URL of the settings page. This issue is fixed in version 2.9.0.

CVSS v3
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
50
EG Risk 50/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)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
0.2%
EPSS %ILE
13th
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 (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-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.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

June 24, 2026

Last Modified

October 25, 2026

Advisory Details (1)

Auto-updated Jun 24, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

Cross-workspace IDOR in AgentTurnResolver · Advisory · twentyhq/twenty · GitHub

https://github.com/twentyhq/twenty/security/advisories/GHSA-v39r-w5vg-j9pp

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 39× 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 178 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 78 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55583?
CVE-2026-55583 is a high-severity vulnerability; its CVE record was published on June 24, 2026. Twenty is an open-source CRM (customer relationship management) platform. Prior to 2.9.0, Twenty was vulnerable to a cross-workspace insecure direct object reference (IDOR) in the AI agent monitor's AgentTurnResolver, in packages/twenty-server/src/engine/metadata-modules/ai/ai-agent-monitor/reso…
When was the CVE record for CVE-2026-55583 published?
The CVE record for CVE-2026-55583 was published on June 24, 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 25, 2026; the record at its source may have been updated since.
Is CVE-2026-55583 actively exploited?
CVE-2026-55583 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55583?
CVE-2026-55583 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55583?
The CVE record for CVE-2026-55583 names the fix: "This issue is fixed in version 2.9.0."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-55583?

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

Book a Demo →Browse All CVEs