CVE-2026-56277

MEDIUMNVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-07-01. NVD baseline CVSS 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
6.5
EG Score
6.5(high)
EPSS
8.0%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 6, 2026

Advisory Details (2)

Auto-updated Jul 3, 2026
Patch available. Sources: github.
generic

Flowise - Hardcoded CORS Wildcard in TTS Endpoint | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flowise-hardcoded-cors-wildcard-in-tts-endpoint
github Patch Available

Hardcoded CORS wildcard on TTS endpoint enables cross-origin credential abuse from any webpage · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-m837-xvxr-vqwg

Vendor Advisories for CVE-2026-56277(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 21:28 UTCEG score recompute▼ 0.40
  2. 2026-07-06 21:28 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 15:52 UTCNVD updateCVSS v3 → 6.5
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-05 22:12 UTCEG score recompute
  9. 2026-07-05 22:11 UTCGHSA enrichment
  10. 2026-07-05 02:31 UTCEPSS rescore
  11. 2026-07-05 02:30 UTCEPSS rescore
  12. 2026-07-04 22:58 UTCEG score recompute
  13. 2026-07-04 22:58 UTCGHSA enrichment
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-03 23:46 UTCEG score recompute
  17. 2026-07-03 23:46 UTCGHSA enrichment
  18. 2026-07-03 00:33 UTCEG score recompute
  19. 2026-07-03 00:33 UTCGHSA enrichment
  20. 2026-07-02 01:21 UTCEG score recompute▲ 6.90
  21. 2026-07-02 01:21 UTCGHSA enrichment
  22. 2026-07-02 01:21 UTCNVD updateCVSS v3 → 6.9 · CVSS v4 → 6.9
  23. 2026-07-01 15:07 UTCEPSS rescore
  24. 2026-07-01 01:20 UTCEG score recompute
  25. 2026-07-01 01:20 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-56277?
CVE-2026-56277 is a medium vulnerability published on July 1, 2026. 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…
When was CVE-2026-56277 disclosed?
CVE-2026-56277 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56277 actively exploited?
CVE-2026-56277 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56277?
CVE-2026-56277 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-56277?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56277, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-56277

Explore →

Is Your Infrastructure Affected by CVE-2026-56277?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs