Skip to main content

CVE-2026-133851flowintel race condition

Low priorityMedium5.3EPSS not scored yet

CVE-2026-133851 is a race condition in flowintel, rated medium (5.3 on CVSS 4.0).

Why this priority: Medium severity, with no exploitation signal.

Published · Updated · NVD status: Received

What it is

Two operations race on shared state, and an attacker who wins the race bypasses a check or corrupts data. An action never checks whether the caller is allowed to perform it.

How it is reached

An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.

What an attacker gains

The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker win a timing window to bypass a check or corrupt shared state.

Is it being exploited?

There is no public report of exploitation yet. It can be exploited automatically, at scale.

What to do

  1. Upgrade flowintel to 4.1.0 or later.
  2. Until it is patched, review who holds accounts that can reach it.

Description from NVD

FlowIntel's alerting module contained an authorization bypass in the alert access control logic. When an alert was linked to a private case, the system relied solely on connector ownership (user or organization) to determine access, without verifying that the requesting user still held valid membership in the associated private case.

This meant that a user who was a connector owner of an alert could continue to read alert details, review history, raw payloads, and action comments, and could perform review-status updates or case-creation actions, even after their access to the linked private case had been revoked or they were never a member of that case.

Additionally, a time-of-check to time-of-use (TOCTOU) gap existed: after a review-status update or a competing case-creation claim was committed, the response could disclose private case identifiers or review history to a user whose access had been concurrently removed by another session linking the alert to a private case.

Impact: - Unauthorized disclosure of private case data (review comments, raw payloads, action history) through alert endpoints. - Unauthorized modification of alert review status and creation of cases from alerts the user should no longer access. - Leakage of a competing case identifier to an unauthorized user during concurrent case-creation races.

Affected versions: FlowIntel prior to 4.1.0.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Request handlers and jobs that share state. The flaw sits between concurrent requests or processes.
  • Permission checks in APIs and admin surfaces. The flaw sits between one role or tenant and another.
  • Multi-tenant services. The flaw sits between one role or tenant and another.

Trust boundaries in play

  • Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
  • Between concurrent requests or processes. An attacker who crosses it can win a timing window to bypass a check or corrupt shared state.
  • Between one role or tenant and another. An attacker who crosses it can reach data or actions their role should not allow.

Questions to answer about your own systems

  • Where does flowintel run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

14-day free trial

Understand how your systems connect.

See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.