CVE-2026-56277

Received Received - Intake

BaseFortify

Publication date: 2026-06-30

Last updated on: 2026-06-30

Assigner: VulnCheck

Description

Flowise before 3.1.2 sets Access-Control-Allow-Origin to a hardcoded wildcard (*) on its text-to-speech (TTS) generation endpoint (packages/server/src/controllers/text-to-speech/index.ts), independent of the server's configured CORS policy. This bypasses the server's otherwise restrictive default CORS configuration (getCorsOptions()) and allows any webpage to make cross-origin requests that trigger TTS generation using stored credentials, enabling drive-by cross-origin credential abuse.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-30

Last Modified

2026-06-30

Generated

2026-07-01

AI Q&A

2026-07-01

EPSS Evaluated

N/A

NVD

CVE-2026-56277

EUVD

EUVD-2026-40432

Affected Vendors & Products

Vendor	Product	Version / Range
flowise	flowise	to 3.1.2 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-346	The product does not properly verify that the source of data or communication is valid.

Attack-Flow Graph

Executive Summary

This vulnerability exists in Flowise versions before 3.1.2, where the text-to-speech (TTS) generation endpoint sets the Access-Control-Allow-Origin header to a hardcoded wildcard (*).

This setting ignores the server's configured CORS policy, which is normally restrictive, and allows any webpage to make cross-origin requests to the TTS endpoint.

As a result, an attacker can cause a user's browser to send requests to the TTS endpoint using the user's stored credentials, enabling drive-by cross-origin credential abuse.

Impact Analysis

This vulnerability can lead to unauthorized use of a user's credentials through cross-origin requests, allowing attackers to trigger TTS generation without the user's consent.

Such drive-by credential abuse can result in misuse of the service, potential data exposure, or other unauthorized actions performed on behalf of the user.

Hi! I’m here to help you understand CVE-2026-56277. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70