PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-52098 FlowiseAI CVE debrief

CVE-2026-52098 is a critical vulnerability in Flowise 3.1.2 that allows remote attackers to execute arbitrary code via the /api/v1/prediction/<flowId> endpoint. The CVSS score is 9.8, indicating a high severity. The CVE record was published on 2026-09-10T17:17:04.940Z and last modified on 2026-09-15T19:09:25.387Z. The NVD entry is currently Analyzed.

Vendor
FlowiseAI
Product
Flowise
CVSS
CRITICAL 9.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-10
Original CVE updated
2026-09-15
Advisory published
2026-09-10
Advisory updated
2026-09-15

Who should care

Defenders responsible for Flowise instances, security teams, and developers should be aware of this vulnerability and assess their exposure. Operational teams managing Flowise deployments, incident response teams, and vulnerability management teams should prioritize verifying exposure and assessing potential impact. Additionally, developers integrating Flowise into their applications should review the vulnerability and implement necessary mitigations.

Why it matters

CVE-2026-52098 is a critical vulnerability in Flowise 3.1.2 that allows remote attackers to execute arbitrary code. Defenders should prioritize verifying exposure and assessing potential impact.

  • Potential arbitrary code execution
  • High severity vulnerability with CVSS score of 9.8
  • Remote attackers can exploit the vulnerability

Technical summary

The vulnerability exists in Flowise 3.1.2 and allows remote attackers to execute arbitrary code via the /api/v1/prediction/<flowId> endpoint, with a CVSS score of 9.8 indicating high severity. This critical vulnerability can lead to significant operational impact if exploited. Defenders should prioritize verifying exposure and assessing potential impact. The technical details indicate a high risk of remote code execution, emphasizing the need for immediate attention and mitigation. Limited information is available on the scope of affected versions and instances, necessitating further verification.

Defensive priority

Defenders should prioritize verifying exposure of Flowise 3.1.2 instances and assessing the potential impact of arbitrary code execution.

Recommended defensive actions

  • Verify exposure of Flowise 3.1.2 instances
  • Assess potential impact of arbitrary code execution
  • Implement compensating controls to limit access to the /api/v1/prediction/<flowId> endpoint
  • Review vendor guidance for Flowise 3.1.2
  • Conduct a thorough review of system logs for potential exploitation
  • Inventory Flowise 3.1.2 deployments for prioritized remediation
  • Monitor for indicators of compromise related to CVE-2026-52098

Evidence notes

The CVE record and NVD detail page provide information on the vulnerability in Flowise 3.1.2, but the scope of affected versions and instances is limited. Defenders should verify exposure and assess potential impact with caution, given limited source information. Evidence from the CVE Program and NVD suggests a critical vulnerability allowing remote code execution via the /api/v1/prediction/<flowId> endpoint. However, additional verification is required to confirm affected deployments and assess operational impact fully.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-52098 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-52098

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-52098 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-52098

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.