Skip to main content
Menu
CVEs

flowintel information disclosure of webhook secrets via alert API

Affects flowintel versions before 4.1.0 for any valid non-admin account, which can read webhook URLs, signing secrets, IMAP credentials and delivery logs. No vendor rating is given. Fixed in 4.1.0.

CVE-2026-133665Published , updated

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.1.0
Who is exposed
Specific setups only

Summary

flowintel exposes webhook URLs, signing secrets, IMAP credentials, and delivery logs, which are meant only for administrators, to authenticated non-admin users through the notification page and alert API. An attacker with a low-privilege account can reach this remotely over the network and may use the credentials to access notification services, impersonate the application in webhook deliveries, or move further into the infrastructure.

Written by a model

Original description

flowintel contains an information disclosure vulnerability that allows authenticated non-administrative users to access sensitive configuration data and logs intended for administrators only.

The notification page and alert API responses exposed sensitive fields, including webhook URLs, signing secrets, IMAP credentials, and delivery logs, in the initial data or JSON responses. Although the user interface hid the configuration form from non-admin users, the underlying data remained accessible via the page source or API endpoints. This exposure included historical webhook URLs that may contain active bearer tokens.

An attacker with a valid non-admin account could retrieve these credentials and logs, potentially leading to unauthorized access to notification services, impersonation of the application in webhook deliveries, or further lateral movement within the infrastructure.

Affected versions: flowintel < 4.1.0

What to do

  1. Check whether your setup matches what the bug needs.

    A valid non-admin user account on flowintel
  2. 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-133665 (flowintel Information Disclosure of Webhook Secrets and Logs to Non-Admin Users), 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-133665 (entry last updated 2026-11-20):
Affected:
- flowintel flowintel: fixed in 4.1.0
Fixed versions: 4.1.0.
Conditions (all must be true for the bug to be hit):
- A valid non-admin user account on flowintel (source: https://github.com/flowintel/flowintel/commit/1445157891add7c04a63e0014cd96bf9802cac66)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-133665 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133665 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/1445157891add7c04a63e0014cd96bf9802cac66
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-133665
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-133665"}.

Affected versions

cve.now Index

15Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • 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 22 if CISA's SSVC rates it automatable

Timeline

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

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

  4. Record last updated

Evidence 3

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

Questions about CVE-2026-133665

Is CVE-2026-133665 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

What does this mean?

Non-admin users can read webhook URLs, which may contain active bearer tokens, along with webhook signing secrets, IMAP credentials and webhook delivery logs. The values can be read from the page source by any authenticated user.

Source: github.com

Which versions are affected by CVE-2026-133665?

flowintel: before 4.1.0.

Source: cve.now feed data

Am I affected, and how do I check?

Flowintel versions from 0 up to, but not including, 4.1.0 are in the affected range. The exposure requires a valid non-admin user account on flowintel, so compare the installed flowintel version with 4.1.0 and check whether non-admin accounts exist.

Source: github.com

How do I fix CVE-2026-133665?

Upgrade flowintel to version 4.1.0 or later, which is the fixed version listed for this vulnerability. The sources name no vendor patch identifiers.

Source: github.com

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