GHSA-x5w6-38gp-mrqh
HIGHGHSA-x5w6-38gp-mrqh is a high-severity (CVSS 7.5) vulnerability in flowise. O3 Security confirms whether GHSA-x5w6-38gp-mrqh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Flowise: Password Reset Link Sent Over Unsecured HTTP
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
flowisenpmDescription
Summary: 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.
Steps to Reproduce:
- Sign up for a new account on https://cloud.flowiseai.com/register.
- Navigate to the https://cloud.flowiseai.com/forgot-password page and enter your email.
- Open your inbox and locate the password reset email.
- Copy the reset link and inspect its protocol – it uses http:// instead of https://.
Impact: If a victim receives this insecure link and uses it over an untrusted network, an attacker can sniff the traffic and capture the reset token. This allows the attacker to hijack the victim's password reset session, potentially compromising their account.
Mitigation: Ensure all sensitive URLs, especially password reset links, are generated and transmitted over secure https:// endpoints only.
Best Practice: Use HTTPS in all password-related email links. Implement HSTS (HTTP Strict Transport Security) to enforce secure connections.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | flowise | all versions | 3.1.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flowise. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update flowise to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x5w6-38gp-mrqh is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-x5w6-38gp-mrqh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-x5w6-38gp-mrqh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-x5w6-38gp-mrqh in your dependencies?
O3 detects GHSA-x5w6-38gp-mrqh across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.