Skip to main content
Menu
CVEs

flowintel auth bypass in Matrix relay allows privilege escalation

CVE-2026-133658EUVD-2026-131452GHSA-8325-PRHG-M22RPublished , updated

6.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 4.1.0
Who is exposed
Not reported

Summary

Flowintel's Matrix relay integration has an authorization flaw that lets an attacker with a low-privileged account, reached remotely over the network, make write changes to cases, tasks, calendar events, templates, and user directory entries that their restricted role should block. Because the relay is recognized by editable profile name and email fields, an ordinary user who sets those fields to match the bot can impersonate the trusted relay and gain its elevated privileges.

Written by a model

Original description

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

What to do

Upgrade to a fixed version: 4.1.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133658 (Flowintel Matrix Relay Authorization Bypass Allows Privilege Escalation and Bot Impersonation), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133658 (entry last updated 2026-11-20):
Affected:
- flowintel flowintel: fixed in 4.1.0
Fixed versions: 4.1.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133658 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133658 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/flowintel/flowintel/commit/48e9e1b847ecd22da11e70829f1ecfaa0df3791d
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133658
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133658"}.

Affected versions

cve.now Index

10Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.3/10CVSS 6.3, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Evidence 3

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133658
RecordNVD · CVE-2026-133658
Other links 1
PatchGitHub · flowintel/flowintel · Commit 48e9e1b8

Questions about CVE-2026-133658

Is CVE-2026-133658 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133658?

flowintel: before 4.1.0.

Source: cve.now feed data

How do I fix CVE-2026-133658?

Upgrade to a fixed version: 4.1.0.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.