CVE-2026-133665: flowintel Information Disclosure of Webhook Secrets and Logs to Non-Admin Users

Published Nov 20, 2026
·
Updated

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

Affected Software

1 affected component
FlowIntel FlowIntel<4.1.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade flowintel to a version that resolves this vulnerability.

    Fixed in 4.1.0

Event History

Nov 20, 2026
CVE Published
via MITRE·10:58 AM
Data Sourced
via MITRE·10:58 AM
RemedyDescriptionWeakness
Data Sourced
via OSV·10:58 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:18 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

FlowIntel versions earlier than 4.1.0 are affected. Version 4.1.0 and later are not listed as affected.

2

What level of access does an attacker need?

An attacker needs a valid authenticated non-administrator account. No administrator privileges or user interaction are required.

3

How can an organization determine whether sensitive data is exposed?

Using a non-administrator account, inspect the notification page source and alert API JSON responses. Affected instances may return webhook URLs, signing secrets, IMAP credentials, delivery logs, and historical webhook URLs even when the configuration form is hidden in the interface.

4

What could exposed webhook data enable?

Historical webhook URLs may contain active bearer tokens. The exposed credentials could enable unauthorized access to notification services, impersonation in webhook deliveries, or lateral movement within the environment.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203