CVE-2026-55583: Twenty: Cross-workspace IDOR in AgentTurnResolver

Published Jun 24, 2026
·
Updated

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.

Affected Software

1 affected component
Twenty Twenty<2.9.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Twenty to a version that resolves this vulnerability.

    Fixed in 2.9.0
  2. Compensating control

    Restrict access to the AI agent monitor settings page (where agentId/turnId UUIDs are exposed in the URL) so that only authorized users for the target workspace can access those URLs, mitigating cross-workspace IDOR while upgrading to 2.9.0.

Event History

Jun 24, 2026
CVE Published
via MITRE·07:21 PM
Data Sourced
via MITRE·07:21 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2026-55583?

CVE-2026-55583 has a severity rating of high at 7.6.

2

How do I fix CVE-2026-55583?

To fix CVE-2026-55583, upgrade Twenty to version 2.9.0 or later.

3

What type of vulnerability is CVE-2026-55583?

CVE-2026-55583 is identified as a cross-workspace insecure direct object reference (IDOR) vulnerability.

4

What are the potential impacts of CVE-2026-55583?

The potential impacts of CVE-2026-55583 include unauthorized access to confidential information across different workspaces.

5

What software is affected by CVE-2026-55583?

CVE-2026-55583 affects the Twenty open-source CRM platform prior to version 2.9.0.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203