Flowise before 3.1.2 sets Access-Control-Allow-Origin to a hardcoded wildcard () on its text-to-speech (TTS) generation endpoint… (CVE-2026-56277)
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.
AI Analysis
Technical Summary
The vulnerability in Flowise prior to version 3.1.2 involves the TTS generation endpoint setting Access-Control-Allow-Origin to '*', ignoring the server's configured CORS options. This misconfiguration enables cross-origin requests from any origin, potentially allowing malicious webpages to abuse stored credentials via drive-by cross-origin requests. The issue is classified under CWE-346 (Origin Validation Error) and has a moderate severity rating. No known exploits are reported in the wild, and the product is not a cloud service.
Potential Impact
An attacker can exploit the misconfigured CORS header to perform cross-origin requests to the TTS generation endpoint with the victim's stored credentials. This could lead to unauthorized use of the TTS functionality and potential credential abuse. The impact is limited to the scope of the TTS endpoint and the credentials accessible in the victim's browser context.
Mitigation Recommendations
A fix is available in Flowise version 3.1.2 that corrects the CORS configuration for the TTS endpoint. Users should upgrade to version 3.1.2 or later to remediate this vulnerability. Since the product is not a cloud service, remediation depends on applying the official fix.
Flowise before 3.1.2 sets Access-Control-Allow-Origin to a hardcoded wildcard () on its text-to-speech (TTS) generation endpoint… (CVE-2026-56277)
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 v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Flowise prior to version 3.1.2 involves the TTS generation endpoint setting Access-Control-Allow-Origin to '*', ignoring the server's configured CORS options. This misconfiguration enables cross-origin requests from any origin, potentially allowing malicious webpages to abuse stored credentials via drive-by cross-origin requests. The issue is classified under CWE-346 (Origin Validation Error) and has a moderate severity rating. No known exploits are reported in the wild, and the product is not a cloud service.
Potential Impact
An attacker can exploit the misconfigured CORS header to perform cross-origin requests to the TTS generation endpoint with the victim's stored credentials. This could lead to unauthorized use of the TTS functionality and potential credential abuse. The impact is limited to the scope of the TTS endpoint and the credentials accessible in the victim's browser context.
Mitigation Recommendations
A fix is available in Flowise version 3.1.2 that corrects the CORS configuration for the TTS endpoint. Users should upgrade to version 3.1.2 or later to remediate this vulnerability. Since the product is not a cloud service, remediation depends on applying the official fix.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-8m62-6r3h-3x25
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-56277"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6a4c344c27e9c797195fbd54
Added to database: 07/06/2026, 23:03:40 UTC
Last enriched: 07/06/2026, 23:28:30 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 14
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.