● High · CVSS 7.5

How to Fix CVE-2026-41275: CWE-319: Cleartext Transmission of Sensitive Information in Flowise

Q: Is CVE-2026-41275 being exploited in the wild?

As of 2026-05-25, CVE-2026-41275 is not listed in the CISA Known Exploited Vulnerabilities catalog. Watch the catalog and patch on a normal cadence; KEV status can change as exploitation evidence emerges.

Q: What is the CVSS score for CVE-2026-41275?

The CVSS base score is 7.5 (High).

Q: What version fixes this?

The vendor advisory names the patched build. See the References section.

Q: Will a WAF or IDS rule alone close this?

No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.

By Sai Kiran Pandrala

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-40893: Arbitrary File Read in gotenberg — Arbitrary File Read in gotenberg
How to Fix CVE-2026-33709: JupyterHub has an Open Redirect in jupyterhub — JupyterHub has an Open Redirect in jupyterhub
How to Fix CVE-2026-2936: Visitor Traffic Real Time Statistics <= 8.4 - Unauthenticated Stored Cross-Site Scripting , Visitor Traffic Real Time Statistics <= 8.4 - Unauthenticated Stored Cross-Site Scripting
How to Fix CVE-2026-22597: Critical Vulnerability in Ghost , Critical Vulnerability in Ghost
How to Fix CVE-2026-4985: Critical Vulnerability in CGIF , Critical Vulnerability in CGIF

Last verified: 2026-05-25

CVE-2026-41275 is a cwe-319: cleartext transmission of sensitive information in FlowiseAI Flowise. Fix it by upgrading to the patched build from the vendor advisory.

⚡ At a glance


Severity	CVSS 7.5 - High
Actively exploited?	Not currently in the CISA KEV catalog
Affected	Flowise < 3.1.0
Fixed in	See vendor advisory
Type (CWE)	CWE-319: CWE-319: Cleartext Transmission of Sensitive Information

What is CVE-2026-41275?

CVE-2026-41275 is a cwe-319: cleartext transmission of sensitive information flaw in FlowiseAI Flowise. It carries a CVSS base score of 7.5 (high). It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

From the source record: Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, the password reset functionality on cloud.flowiseai.com sends a reset password link over the unsecured HTTP protocol instead of HTTPS. This behavior introduces the risk of a man-in-the-middle (MITM) attack, where an attacker on the same network as the user (e.g., public Wi-Fi) can intercept the reset link and gain unauthorized access to the victim’s account. This vulnerability is fixed in 3.1.0.

Why it matters in practice: The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.

Am I affected?

You are affected if your installation of Flowise matches a version listed in the Affected row above.

Check the running version against the Affected row above using the product's admin console or --version flag.

How to fix CVE-2026-41275

Apply the vendor patch. Target the build named in the Fixed in row above (See vendor advisory). The runnable command set below covers the most common deployment patterns for Flowise.

Generic upgrade pattern

If the affected product is a Linux package, upgrade via the system package manager:


# Debian / Ubuntu
sudo apt-get update && sudo apt-get upgrade -y

# RHEL / Rocky / Alma
sudo dnf upgrade --security -y

If it ships as a Windows installer, download the patched build from the vendor advisory and:


# Vendor advisory: https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-x5w6-38gp-mrqh
Start-Process msiexec.exe -ArgumentList '/i <patched-installer>.msi /qn /norestart' -Wait
Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | \
    Where-Object DisplayName -match '<product-name>' | Select-Object DisplayName, DisplayVersion

After applying the patch

Restart the service or device so the patched binary loads.
Confirm the running version matches the Fixed in row using the verification command below.
Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.

If you can't patch immediately

Until the patch lands, narrow the attack surface with these runnable controls.

Restrict network exposure

Block public access to the affected service at the perimeter. Allow only trusted source IPs.


# Linux iptables: only allow trusted admin subnet
sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4


# Windows firewall: only allow trusted admin subnet on management port
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Allow" -Direction Inbound -Action Allow `
  -RemoteAddress 10.10.10.0/24 -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Deny"  -Direction Inbound -Action Block `
  -Protocol TCP -LocalPort 443

Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.

How to verify the fix worked

Confirm the patched build is the one actually running.

Check the running version against the Affected row above using the product's admin console or --version flag.

Expected: a version at or above the patched build named in the vendor advisory.

Also worth doing: pull recent log windows for indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.

Frequently asked questions

Is CVE-2026-41275 being exploited in the wild?