CVE-2025-8943

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because EPSS predicts 88% probability of exploitation within the next 30 days (top 0.5% of all CVEs). NVD baseline CVSS 9.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 72%
CISA-KEV: Not listedEPSS: 72%CVSS: 9.8Exploit: NoneExposed: 0

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

The Custom MCPs feature is designed to execute OS commands, for instance, using tools like npx to spin up local MCP Servers. However, Flowise's inherent authentication and authorization model is minimal and lacks role-based access controls (RBAC). Furthermore, in Flowise versions before 3.0.1 the default installation operates without authentication unless explicitly configured. This combination allows unauthenticated network attackers to execute unsandboxed OS commands.

CVSS v3
9.8
EG Score
9.8(high)
EPSS
99.4%
KEV
Not listed

Published

August 14, 2025

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Jul 12, 2026
No patch confirmed yet.
generic

Flowise OS command remote code execution | JFSA-2025-001380578 - JFrog Security Research

https://research.jfrog.com/vulnerabilities/flowise-os-command-remote-code-execution-jfsa-2025-001380578/

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
npmflowiseghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
flowise

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 33× 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.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-15 01:59 UTCEPSS rescore
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-07 13:46 UTCEPSS rescore
  11. 2026-07-06 16:51 UTCOSV refresh
  12. 2026-07-06 02:23 UTCEPSS rescore
  13. 2026-07-05 02:30 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-04 06:31 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-27 03:08 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-25 13:49 UTCEPSS rescore
  22. 2026-06-24 14:05 UTCEPSS rescore
  23. 2026-06-24 14:04 UTCEPSS rescore
  24. 2026-06-23 21:32 UTCEPSS rescore
  25. 2026-06-21 14:56 UTCEPSS rescore
Show 31 more
  1. 2026-06-21 14:56 UTCEPSS rescore
  2. 2026-06-21 01:59 UTCEPSS rescore
  3. 2026-06-21 01:59 UTCEPSS rescore
  4. 2026-06-18 17:52 UTCEPSS rescore
  5. 2026-06-18 17:52 UTCEPSS rescore
  6. 2026-06-18 05:13 UTCOSV refresh
  7. 2026-06-17 17:53 UTCEPSS rescore
  8. 2026-06-16 17:52 UTCEPSS rescore
  9. 2026-06-15 17:48 UTCEPSS rescore
  10. 2026-06-13 23:00 UTCEPSS rescore
  11. 2026-06-13 23:00 UTCEPSS rescore
  12. 2026-06-12 23:12 UTCEPSS rescore
  13. 2026-06-12 23:12 UTCEPSS rescore
  14. 2026-06-11 14:00 UTCEPSS rescore
  15. 2026-06-10 22:18 UTCEPSS rescore
  16. 2026-06-10 13:22 UTCEPSS rescore
  17. 2026-06-06 13:47 UTCEPSS rescore
  18. 2026-06-06 13:47 UTCEPSS rescore
  19. 2026-06-05 22:47 UTCEPSS rescore
  20. 2026-06-05 22:46 UTCEPSS rescore
  21. 2026-06-05 06:10 UTCEPSS rescore
  22. 2026-06-05 06:10 UTCEPSS rescore
  23. 2026-06-04 13:12 UTCEPSS rescore
  24. 2026-06-04 13:12 UTCEPSS rescore
  25. 2026-06-02 20:13 UTCEPSS rescore
  26. 2026-06-01 13:51 UTCEPSS rescore
  27. 2026-06-01 13:51 UTCEPSS rescore
  28. 2026-05-30 00:22 UTCEG score recompute
  29. 2026-05-30 00:22 UTCGHSA enrichment
  30. 2026-05-29 13:44 UTCEPSS rescore
  31. 2026-05-29 13:44 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitexploit/multi/http/flowise_custommcp_rce✓ verified
    First seen Aug 14, 2025

    Flowise Custom MCP Remote Code Execution

    Open source ↗
  • Nucleihttp/cves/2025/CVE-2025-8943.yaml
    First seen Jan 1, 2025

    Flowise < 3.0.1 - Remote Command Execution

    Open source ↗

Frequently asked(5)

What is CVE-2025-8943?
CVE-2025-8943 is a critical vulnerability published on August 14, 2025. The Custom MCPs feature is designed to execute OS commands, for instance, using tools like npx to spin up local MCP Servers. However, Flowise's inherent authentication and authorization model is minimal and lacks role-based access controls (RBAC). Furthermore, in Flowise versions before 3.0.1 the…
When was CVE-2025-8943 disclosed?
CVE-2025-8943 was first published in the National Vulnerability Database on August 14, 2025, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-8943 actively exploited?
CVE-2025-8943 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-8943?
CVE-2025-8943 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-8943?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-8943, 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-2025-8943

Explore →

Is Your Infrastructure Affected by CVE-2025-8943?

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