Vulnerability report

Active exploitation observed Confirmed confidence Not in CISA KEV

CVE-2025-8943

Flowise Remote Code Execution

Flowise / Flowise · affected before 3.0.1

Severity
CVSS 9.8 · Critical
Confidence
Confirmed
Exploit status
Observed in sensors
EPSS
72.3%
First observed
10 Jul 2026
Last observed
18 Aug 2026

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2025-8943 is an unauthenticated vulnerability affecting Flowise Flowise. The Custom MCPs feature is designed to execute OS commands, for instance, using tools like `npx` to spin up local MCP Servers. However,...

Is it exploited?

Yes. KEV Intelligence sensors observed exploitation attempts with confirmed confidence.

Who is affected?

Flowise / Flowise affected before 3.0.1.

What should we do?

Patch immediately, validate internet-facing exposure, and monitor for matching requests.

Overview

Flowise Remote Code Execution

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.

Vendor Product Affected Status
flowise Before 3.0.1 Affected
View vendor advisory (opens in new tab)
Published
14 Aug 2025
Exploitation Reported
10 Jul 2026
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

nuclei_scanner

CVE References

Exploitation evidence

Why KEV Intelligence marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

KEV Intelligence

Recorded 10 Jul 2026

Independent exploitation attestation added to the KEV Intelligence record.

Active exploitation observed

KEV Intelligence sensor

First observed 10 Jul 2026

First-party sensor telemetry confirms matching exploitation attempts.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the KEV Intelligence Pro API.

Learn about Pro API access
Source Added
KEV Intelligence First 2026-08-05 08:45 UTC

Operational indicators for this CVE are listed under Detection.

Sensor telemetry

First-party evidence of exploitation activity

Aggregate observations show the scale, recency, and distribution of activity without overstating sparse data.

53

Attempts observed

26

Unique attacker IPs

12

Attacker countries

BN · CN · GB · HK · IL · IN · IR · JP · NL · SG · US · VN

5

Sensors observed

Exploitation attempts over the last 42 days

Daily events observed by KEV Intelligence sensors

Updated 19 Aug 2026

0
2
3
0
0
0
0
12
3
3
2
0
2
1
3
9
0
0
0
3
0
2
3
0
0
0
0
1
0
0
1
2
1
1
2
5
6
1
2
6
2
0
9 Jul 18 Jul 27 Jul 5 Aug 19 Aug

First observed 10 Jul 2026 · Last observed 18 Aug 2026

Pro adds sensor region and window summaries. Enterprise adds raw IPs, paths, User-Agents, and payloads.

Request telemetry access

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
1
User-Agents
28

Raw values available in Pro and Enterprise.

Virtual patch status

No KEV Intelligence virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

Attacker IP Indicators

Attacker IP indicators observed · available in Pro and Enterprise.

Sensor-derived attacker IP indicators are available to Pro and Enterprise accounts under Detection and through the Pro API.

Learn about Pro API access

Scanner Artifacts

Scanner and exploit-framework references linked to this CVE.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

72.3%

Recent mention · Github Advisory Database (NPM)

[flowise-components] Flowise: CVE-2025-8943 Patch Bypass: npm_config_yes bypasses MCP environment variable blocklist (Unauthenticated RCE)

Summary The mitigation shipped for CVE-2025-8943 blocks the -y and --yes flags on npx to stop auto-installation of arbitrary packages. That flag filter works. The environment-variable check in the same patch denies only four variable names by exact string match, and npm reads...

Read full advisory

All Mentions

Recent mention · Github Advisory Database (NPM)

[flowise-components] Flowise: CVE-2025-8943 Patch Bypass: npm_config_yes bypasses MCP environment variable blocklist (Unauthenticated RCE)

Github Advisory Database (NPM) · 04 Aug 2026

Summary The mitigation shipped for CVE-2025-8943 blocks the -y and --yes flags on npx to stop auto-installation of arbitrary packages. That flag filter works. The environment-variable check in the same patch denies only four variable names by exact string match, and npm reads its configuration directly from npm_config_* environment variables. Setting npm_config_yes=true reproduces the --yes behaviour the flag filter is meant to prevent, so npx auto-installs and executes the named package. The mitigation is fully bypassed. This works with the MCP security check enabled...

Recent mention · Github Advisory Database (NPM)

[flowise] Flowise: CVE-2025-8943 Patch Bypass: npm_config_yes bypasses MCP environment variable blocklist (Unauthenticated RCE)

Github Advisory Database (NPM) · 04 Aug 2026

Summary The mitigation shipped for CVE-2025-8943 blocks the -y and --yes flags on npx to stop auto-installation of arbitrary packages. That flag filter works. The environment-variable check in the same patch denies only four variable names by exact string match, and npm reads its configuration directly from npm_config_* environment variables. Setting npm_config_yes=true reproduces the --yes behaviour the flag filter is meant to prevent, so npx auto-installs and executes the named package. The mitigation is fully bypassed. This works with the MCP security check enabled...

Potential Proof of Concepts

These PoCs are unverified and could contain malware. Use at your own risk.

Timeline

From disclosure to observed exploitation

  1. Observed by KEV Intelligence sensors

    Evidence-backed exploitation signal

  2. Indicators of compromise added (40)

    Indicators of compromise recorded

  3. Public PoC available

    Public proof-of-concept code published

  4. Nuclei template available

    Scanner coverage available

  5. CVE published

    Vulnerability disclosed publicly

  6. CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2025-8943

Free JSON includes basic KEV fields
{
  "cve_id": "CVE-2025-8943",
  "confidence": "Confirmed",
  "cvss_score": 9.8,
  "cvss_estimated": false,
  "epss_score": 0.7231,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": true
  },
  "sensor_telemetry": { "attempts": 53, "sensors": 5 }
}

Early warning alerts

Get alerts on high-impact exploitation

Receive curator-selected alerts when exploitation activity warrants attention. Each alert includes the evidence and context needed to decide what requires attention now.

Occasional high-impact alerts. Unsubscribe anytime. See our Privacy Policy.