CVE-2026-133658: Flowintel Matrix Relay Authorization Bypass Allows Privilege Escalation and Bot Impersonation
Flowintel contains a privilege escalation vulnerability in its Matrix relay (bot) integration. When the relay forwarded API requests on behalf of a represented user, the authorization and permission checks evaluated the relay bot's elevated role while the request handlers acted as the lower-privileged represented user. This mismatch allowed users with restricted roles (e.g., Read Only) to perform write operations, directory lookups, calendar modifications, assignment changes, template creation, and import actions they were not authorized to perform.
Additionally, relay authority was determined by matching editable user profile fields (name and email) rather than a protected, non-spoofable identifier. An ordinary user who modified their profile to match the expected bot name could be recognized as the trusted relay, enabling impersonation of the bot and potential access to its elevated privileges.
Preconditions: - A valid Flowintel user account with a restricted role (e.g., Read Only) - Access to the Matrix relay integration or the ability to send API requests with the relay's API key and a MATRIX-ID header - For the impersonation vector: ability to edit one's own profile name fields
Security impact: - Unauthorized write operations by users with read-only or otherwise restricted permissions - Potential impersonation of the trusted relay bot by ordinary users - Bypass of organization-level access controls and role-based restrictions - Unauthorized modification of cases, tasks, calendar events, templates, and user directory entries
Affected versions: Flowintel prior to 4.1.0
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Flowintelto a version that resolves this vulnerability.Fixed in 4.1.0 - Operational
Use bin/register_matrix_bot.py to register Matrix bot accounts by ID instead of relying on editable profile fields.
Event History
Frequently Asked Questions
Who can exploit the authorization bypass?
An attacker needs a valid Flowintel account assigned a restricted role, such as Read Only. They must also have access to the Matrix relay integration or be able to send API requests using the relay API key and a MATRIX-ID header.
What actions could a restricted user perform through the vulnerable relay path?
A restricted user could perform operations normally requiring greater privileges, including write actions, directory lookups, calendar modifications, assignment changes, template creation, and imports.
What is required to impersonate the Matrix relay bot?
The impersonation vector requires an ordinary user to be able to edit their own profile name field. Because relay authority was matched against editable name and email profile fields, changing a profile to match the expected bot name could cause the user to be recognized as the trusted relay.
How can teams identify potential exposure or prior abuse?
Review Matrix relay-originated API activity for requests attributed to restricted users that performed write operations, directory lookups, calendar changes, assignment changes, template creation, or imports. Also review user profile changes for names or emails matching the expected relay bot identity.