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

Summary

Flowise's TTS generation endpoint hardcodes `Access-Control-Allow-Origin: *` in packages/server/src/controllers/text-to-speech/index.ts (line 83), independent of the server's CORS configuration. This lets any webpage make cross-origin requests that generate speech using stored credentials, bypassing the restrictive default `getCorsOptions()` policy. Combined with Finding 3 (TTS credential abuse), it enables drive-by credential abuse via malicious webpages.

Mitigation

Remove the hardcoded CORS wildcard and let the server's CORS middleware handle the headers. Delete the lines `res.setHeader('Access-Control-Allow-Origin', '*')` and `res.setHeader('Access-Control-Allow-Headers', 'Cache-Control')`.

Affected packages in the Exposure Registry

Matched by package name and ecosystem. Each entry shows whether the package delegates to a language model and how many tracked packages depend on it.

• flowisenpmLLM dependency since 2024-03-12

Related items

• MediumWhen LLM Gateways Go Wrong: Findings from LiteLLMSimilar attack · Check Point Research
• HighCVE-2026-109403: conductor-oss conductor server-side request forgery in agent card fetchingSimilar attack · NVD/CVE Database
• InfoExploring Backdoor Vulnerabilities and Fairness Challenges in Generative Models: A SurveySimilar attack · ACM Digital Library (TOPS, DTRAP, CSUR)
• LowSmall AI Models Could Soon Self-Replicate on IoT Devices, Anthropic WarnsSimilar attack · SecurityWeek
• MediumCVE-2026-108940: Mistral.rs path traversal through calibration_apply save_cimatrix argumentSimilar attack · NVD/CVE Database