Cyber Resilience

CVE-2026-73601

RCE

Public PoCRCE
Published
13 August 2026
Modified
14 August 2026
CVSS Score v4 9.0
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0061 46th percentile
Risk Priority 40 floored blend · peak EPSS

Summary

CVE-2026-73601 is a critical-severity Eval Injection (CWE-95) vulnerability. Its CVSS base score is 9.0 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique JavaScript (T1059.007); ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

This vulnerability is AI-related — categorised as AI Agent Protocols and Integrations; in the Protocol-Specific Risks risk domain.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

Flowise versions before 3.1.3 contain a remote code execution vulnerability in the Custom MCP node when CUSTOM_MCP_PROTOCOL is set to stdio, allowing authenticated users to execute arbitrary commands by manipulating environment variables and command arguments. Attackers can abuse PYTHONWARNINGS and…

more

BROWSER environment variables with python3, or leverage the root working directory with node to bypass validation and execute system commands.

CWE(s)
CWE-95

AI Security AnalysisAI

AI Category
AI Agent Protocols and Integrations
Risk Domain
Protocol-Specific Risks
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
Matched keywords: mcp

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059.007 JavaScript Execution
Adversaries may abuse various implementations of JavaScript for execution.
attack.mitre.org →
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
attack.mitre.org →
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
attack.mitre.org →
T1059.005 Visual Basic Execution
Adversaries may abuse Visual Basic (VB) for execution.
attack.mitre.org →
T1059.006 Python Execution
Adversaries may abuse Python commands and scripts for execution.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-42079Shared CWE-95
CVE-2024-32647Shared CWE-95
CVE-2026-67195Shared CWE-95
CVE-2026-53875Shared CWE-95
CVE-2026-15971Shared CWE-95
CVE-2025-43466Shared CWE-95
CVE-2025-0868Shared CWE-95
CVE-2025-68271Shared CWE-95
CVE-2026-50733Shared CWE-95
CVE-2025-65530Shared CWE-95

Affected Assets

—
Flowise
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.2

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and code analysis can discover eval-injection flaws but does not stop their introduction.

SI-10 Information Input Validation good match

Input validation explicitly requires neutralizing untrusted data before it reaches dynamic evaluation constructs such as eval.

SA-15 Development Process, Standards, and Tools partial match

Secure-development standards and tools can mandate safe coding patterns that avoid unsafe dynamic evaluation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization and avoidance of unsafe dynamic evaluation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect eval injection vulnerabilities before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and safe coding practices that directly prevent eval injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements include rules against dynamic code execution of untrusted input.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles discourage unsafe dynamic evaluation constructs.

A.8.28 Secure coding partial match
prevents

Secure coding explicitly requires neutralization of input before dynamic evaluation, directly mitigating eval injection.

A.8.31 Separation of development, test and production environments none match
none

Separation of environments limits the blast radius if eval injection occurs in non-production.

References