CVE-2026-41268

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.4%, top 19% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 14%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, Flowise is vulnerable to a critical unauthenticated remote command execution (RCE) vulnerability. It can be exploited via a parameter override bypass using the FILE-STORAGE:: keyword combined with a NODE_OPTIONS environment variable injection. This allows for the execution of arbitrary system commands with root privileges within the containerized Flowise instance, requiring only a single HTTP request and no authentication or knowledge of the instance. This vulnerability is fixed in 3.1.0.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
96.1%
KEV
Not listed

Published

April 23, 2026

Last Modified

April 24, 2026

Advisory Details (1)

Auto-updated May 11, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Flowise Parameter Override Bypass Remote Command Execution · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-cvrr-qhgw-2mm6

Affected Packages

(2 across 1 ecosystem)
npm(2)
PackageVulnerable rangeFixed inDependents
flowise—3.1.0—
flowise-components—3.1.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 136 total refreshes for this CVE.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-08 15:15 UTCEPSS rescore
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-01 15:06 UTCEPSS rescore
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-28 04:56 UTCEPSS rescore
  13. 2026-06-27 03:08 UTCEPSS rescore
  14. 2026-06-25 13:49 UTCEPSS rescore
  15. 2026-06-25 13:49 UTCEPSS rescore
  16. 2026-06-24 14:05 UTCEPSS rescore
  17. 2026-06-23 21:33 UTCEPSS rescore
  18. 2026-06-22 14:25 UTCEPSS rescore
  19. 2026-06-22 14:25 UTCEPSS rescore
  20. 2026-06-21 14:56 UTCEPSS rescore
  21. 2026-06-21 14:56 UTCEPSS rescore
  22. 2026-06-21 01:59 UTCEPSS rescore
  23. 2026-06-19 19:25 UTCEPSS rescore
  24. 2026-06-18 17:52 UTCEPSS rescore
  25. 2026-06-18 17:52 UTCEPSS rescore
Show 75 more
  1. 2026-06-17 17:53 UTCEPSS rescore
  2. 2026-06-16 17:52 UTCEPSS rescore
  3. 2026-06-15 17:49 UTCEPSS rescore
  4. 2026-06-15 06:42 UTCEG score recompute
  5. 2026-06-15 02:24 UTCEG score recompute
  6. 2026-06-14 20:59 UTCEG score recompute
  7. 2026-06-14 16:42 UTCEG score recompute
  8. 2026-06-14 12:17 UTCEG score recompute
  9. 2026-06-13 23:00 UTCEPSS rescore
  10. 2026-06-12 23:12 UTCEPSS rescore
  11. 2026-06-12 23:12 UTCEPSS rescore
  12. 2026-06-12 12:25 UTCEG score recompute
  13. 2026-06-12 07:42 UTCEG score recompute
  14. 2026-06-12 03:11 UTCEG score recompute
  15. 2026-06-11 22:57 UTCEG score recompute
  16. 2026-06-11 18:39 UTCEG score recompute
  17. 2026-06-11 14:24 UTCEG score recompute
  18. 2026-06-11 14:00 UTCEPSS rescore
  19. 2026-06-10 22:18 UTCEPSS rescore
  20. 2026-06-10 21:15 UTCEG score recompute
  21. 2026-06-10 17:00 UTCEG score recompute
  22. 2026-06-10 13:22 UTCEPSS rescore
  23. 2026-06-10 13:22 UTCEPSS rescore
  24. 2026-06-10 12:43 UTCEG score recompute
  25. 2026-06-10 08:27 UTCEG score recompute
  26. 2026-06-10 04:12 UTCEG score recompute
  27. 2026-06-09 23:57 UTCEG score recompute
  28. 2026-06-09 18:14 UTCEG score recompute
  29. 2026-06-09 13:59 UTCEG score recompute
  30. 2026-06-09 09:45 UTCEG score recompute
  31. 2026-06-09 03:22 UTCEG score recompute
  32. 2026-06-08 14:33 UTCEG score recompute
  33. 2026-06-08 14:17 UTCEPSS rescore
  34. 2026-06-08 14:17 UTCEPSS rescore
  35. 2026-06-08 10:18 UTCEG score recompute
  36. 2026-06-08 06:03 UTCEG score recompute
  37. 2026-06-08 01:47 UTCEG score recompute
  38. 2026-06-07 21:33 UTCEG score recompute
  39. 2026-06-07 17:18 UTCEG score recompute
  40. 2026-06-07 15:25 UTCEPSS rescore
  41. 2026-06-07 15:25 UTCEPSS rescore
  42. 2026-06-07 13:02 UTCEG score recompute
  43. 2026-06-07 08:46 UTCEG score recompute
  44. 2026-06-07 04:31 UTCEG score recompute
  45. 2026-06-06 22:48 UTCEG score recompute
  46. 2026-06-06 18:03 UTCEG score recompute
  47. 2026-06-06 13:47 UTCEPSS rescore
  48. 2026-06-06 13:47 UTCEPSS rescore
  49. 2026-06-06 13:43 UTCEG score recompute
  50. 2026-06-06 09:28 UTCEG score recompute
  51. 2026-06-06 05:09 UTCEG score recompute
  52. 2026-06-06 00:54 UTCEG score recompute
  53. 2026-06-05 22:47 UTCEPSS rescore
  54. 2026-06-05 20:39 UTCEG score recompute
  55. 2026-06-05 16:24 UTCEG score recompute
  56. 2026-06-05 11:49 UTCEG score recompute
  57. 2026-06-05 07:15 UTCEG score recompute
  58. 2026-06-05 06:10 UTCEPSS rescore
  59. 2026-06-05 06:10 UTCEPSS rescore
  60. 2026-06-05 03:00 UTCEG score recompute
  61. 2026-06-04 20:27 UTCEG score recompute
  62. 2026-06-04 16:00 UTCEG score recompute
  63. 2026-06-04 13:12 UTCEPSS rescore
  64. 2026-06-04 13:12 UTCEPSS rescore
  65. 2026-06-04 11:45 UTCEG score recompute
  66. 2026-06-04 00:53 UTCEG score recompute
  67. 2026-06-03 20:36 UTCEG score recompute
  68. 2026-06-03 16:19 UTCEG score recompute
  69. 2026-06-03 12:04 UTCEG score recompute
  70. 2026-06-03 02:19 UTCEG score recompute
  71. 2026-06-02 20:46 UTCEG score recompute
  72. 2026-06-02 20:13 UTCEPSS rescore
  73. 2026-06-02 16:30 UTCEG score recompute
  74. 2026-06-02 12:15 UTCEG score recompute
  75. 2026-06-02 03:06 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41268?
CVE-2026-41268 is a critical vulnerability published on April 23, 2026. Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, Flowise is vulnerable to a critical unauthenticated remote command execution (RCE) vulnerability. It can be exploited via a parameter override bypass using the FILE-STORAGE:: keyword combined…
When was CVE-2026-41268 disclosed?
CVE-2026-41268 was first published in the National Vulnerability Database on April 23, 2026, with the most recent update on April 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41268 actively exploited?
CVE-2026-41268 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41268?
CVE-2026-41268 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-41268?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41268, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41268

Explore →

Is Your Infrastructure Affected by CVE-2026-41268?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs