gcdRadar
archive/Patch now/AIR-2026-0714
closedclosed 20 May 2026Patch now2 Disclosed vulnerabilityAI

Flowise hardcoded CORS wildcard on TTS endpoint

Flowise

A hardcoded CORS wildcard header on the Flowise text-to-speech endpoint enables cross-origin credential abuse. Arbitrary webpages can trigger speech generation using stored server credentials.

disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why

fix status
Fix status unknown
first report
20 May 2026
last update
20 May 2026

Timeline · 1

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

Sources · 1

Advisories and databases

  1. 2026-05-20

Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.

Classification

AI role
Attack on AI
categories
Infrastructure vulnerability
severity
2 · Disclosed vulnerability
fix status
Fix status unknown
targets
Framework / tooling
owasp llm top 10
LLM03:2025 Supply Chain
mitre atlas
no technique for these categories
dates
happened 20 May 2026 · first reported 20 May 2026
origin
GitHub Advisory Database
Vulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
record
confidence 0.95 · created 2026-10-18 07:00Z · updated 2026-10-18 10:14Z

Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned

Copy a brief

This record as a short Markdown brief, for a ticket, a chat or a coding agent.

the brief as text
# Flowise hardcoded CORS wildcard on TTS endpoint

https://gcdradar.vercel.app/incidents/ghsa-m837-xvxr-vqwg-flowise-hardcoded-cors-wildcard-on-tts-e · AIR-2026-0714 · closed 2026-05-20

- Lane: Patch now
- Severity: 2 (Disclosed vulnerability)
- Fix status: Fix status unknown
- First reported: 2026-05-20
- AI role: Attack on AI
- Products: Flowise

## Summary

A hardcoded CORS wildcard header on the Flowise text-to-speech endpoint enables cross-origin credential abuse. Arbitrary webpages can trigger speech generation using stored server credentials.

## What to do

No action recorded; read the sources below and the vendor's advisory.

## Latest updates

- 2026-05-20: GHSA-m837-xvxr-vqwg: Flowise: Hardcoded CORS wildcard on TTS endpoint enables cross-origin credential abuse from any webpage (https://github.com/advisories/GHSA-m837-xvxr-vqwg)

## Sources

- 2026-05-20 GitHub Advisory Database: GHSA-m837-xvxr-vqwg: Flowise: Hardcoded CORS wildcard on TTS endpoint enables cross-origin credential abuse from any webpage https://github.com/advisories/GHSA-m837-xvxr-vqwg

Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.

Related

  1. closed7.7
    Flowise CVE-2026-56268: Flowise cross-workspace chatflow information disclosure

    Patch now · Disclosed · since 20 May 2026 · updated 22 Jun 2026 · CVE-2026-56268

    AI
  2. closed
    Flowise Flowise mass assignment password override vulnerability

    Patch now · Disclosed · since 20 May 2026

    AI
  3. closed
    Flowise Flowise MCP security bypass leads to RCE

    Patch now · Disclosed · since 14 May 2026

    AI
  4. closed5.3
    Flowise CVE-2026-8027: Authorization bypass in FlowiseAI Flowise user controller handler

    Patch now · Disclosed · since 6 May 2026 · CVE-2026-8027

    AI
  5. closed3.7
    Flowise CVE-2026-8028: Information disclosure vulnerability in FlowiseAI Flowise

    Patch now · Disclosed · since 6 May 2026 · CVE-2026-8028

    AI
  6. closed6.3
    Flowise Flowise API response handler exposes bcrypt password hashes

    Patch now · Disclosed · since 6 May 2026 · CVE-2026-8026

    AI