INCIDENT MAP

Browse / AI Framework and Platform Flaws / CVE-2026-56277

Flowise: Hardcoded CORS wildcard on TTS endpoint enables cross-origin credential abuse from any webpage

CVE-2026-56277 · 2026-05-20 moderate

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Cross-site request forgery
Affected
flowise (npm)
CVSS
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
EPSS
0.2% chance of exploitation in 30 days

How it works, in short

A hardcoded wildcard CORS header on the TTS endpoint lets any website make cross-origin requests that use stored credentials. (Our summary, written by a model. The source text is below.)

Details

Summary

The TTS generation endpoint sets Access-Control-Allow-Origin: * as a hardcoded response header, independent of the server's CORS configuration. This enables any webpage to make cross-origin requests to generate speech using stored credentials.

Root Cause

// packages/server/src/controllers/text-to-speech/index.ts:83
res.setHeader('Access-Control-Allow-Origin', '*')
res.setHeader('Access-Control-Allow-Headers', 'Cache-Control')

Impact

Suggested Fix

Remove the hardcoded CORS wildcard and let the server's CORS middleware handle the headers:

// Remove these lines:
// res.setHeader('Access-Control-Allow-Origin', '*')
// res.setHeader('Access-Control-Allow-Headers', 'Cache-Control')

---

References

References

Source: GitHub Advisory Database, used under CC BY 4.0.