Quick answers
- Is CVE-2026-55583 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55583 being exploited in the wild.
- How severe is CVE-2026-55583?
- High severity, with a CVSS score of 7.6, published 24 June 2026.
- Which products and versions are affected?
- Twenty < 2.9.0.
- Is there a fix for CVE-2026-55583?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-55583 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-55583?
- 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
A cross-workspace Insecure Direct Object Reference (IDOR) exists in the AgentTurnResolver and agent-turn-grader.service.ts. The root cause is that the agentTurns query and evaluateAgentTurn mutation perform database lookups using only agentId or id without verifying the workspaceId, even though the AgentTurnEntity contains a workspaceId column. While class-level guards ensure a user is authenticated, they fail to verify that the requested object belongs to the user's specific workspace. An attacker with low privileges (authenticated with AI settings access) can retrieve full chat histories or insert evaluation rows for other workspaces if they obtain the victim's non-guessable UUIDs (which may be exposed in URLs). This issue is resolved in version 2.9.0.
Affected products
- twentyhq Twenty < 2.9.0
Timeline
- 2026-06-17: advisory: GitHub advisory published
- 2026-06-24: disclosed: NVD publication date