How broadly exploitable is this vulnerability?

Any user or script that can reach the affected Flowise instance and knows or can guess a public chatflow or chatbot ID may retrieve full configuration data, including secrets, without authentication. The scope encompasses all secrets stored in public chatflows.

What level of access does an attacker need to exploit this issue?

Only network access to the Flowise public endpoints is required. There is no need for a valid user account if the chatflow or chatbot is configured as public; access is based on the ability to call the public API with a valid identifier.

What is the safest general pattern to fix this vulnerability class?

Implement a strict separation between internal configuration and public representations: define explicit response schemas for public endpoints, whitelist only non-sensitive fields, and ensure all secret-bearing fields are excluded or replaced with non-sensitive references before serialization.

Severity:

HIGH RISK

(7.5)

Information Exposure via Unsanitized Public API (CWE-200) in Flowise Public Chatflows

CVE-2026-41278

Published:

Apr 23, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-74;CWE-89

HIGH RISK

HIGH

(7.3)

SQL Injection via Unsanitized ID Parameter (CWE-89) in Pharmacy Sales and Inventory System /ajax.php

Database Compromise and Data Integrity Loss

April 27, 2026

CWE-863

HIGH RISK

HIGH

(8.5)

Incorrect Authorization (CWE-863) in OpenClaw chat.send Session Management

Privilege Escalation and Unauthorized Session Control

April 27, 2026

Vulnerability Type

Category:

Information Exposure

CWE:

CWE-200

Impact:

Sensitive Data Disclosure

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Vulnerability Type

Category:

Information Exposure

CWE:

CWE-200

Impact:

Sensitive Data Disclosure

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Information Exposure via Unsanitized Public API (CWE-200) in Flowise Public Chatflows

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(7.3)

SQL Injection via Unsanitized ID Parameter (CWE-89) in Pharmacy Sales and Inventory System /ajax.php

HIGH RISK

HIGH

(8.5)

Incorrect Authorization (CWE-863) in OpenClaw chat.send Session Management

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare