Medium 6.9Published Jun 30, 2026

CVE-2026-56277Flowise - Hardcoded CORS Wildcard in TTS Endpoint

Updated under an hour ago (Oct 27, 2026, 12:40 PM ET)

Does this affect you?

It affects Flowise and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Flowise

Exploited in the last 30 days

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: 6.9 MEDIUM (v4.0, CNA)CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Weakness (CWE): CWE-346
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: VulnCheck
NVD analysis: Analyzed
Record last updated: Jul 1, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Flowise Flowise flowise:flowise (from the name)	before 3.1.2; 3.1.2 not affected	CNA record
flowiseai flowise flowiseai:flowise	before 3.1.2	NVD

References

References

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-m837-xvxr-vqwg	vendor-advisory, mitigation
https://www.vulncheck.com/advisories/flowise-hardcoded-cors-wildcard-in-tts-endpoint	third-party-advisory

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.