CVE-2026-56277

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM 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 — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 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(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
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.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
flowise—3.1.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 83× 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.

Showing the most recent 100 of 144 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 05:49 UTCEG score recompute
  3. 2026-08-25 05:49 UTCGHSA enrichment
  4. 2026-08-24 06:36 UTCGHSA enrichment
  5. 2026-08-23 06:44 UTCEG score recompute
  6. 2026-08-23 06:43 UTCGHSA enrichment
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-22 07:31 UTCEG score recompute
  9. 2026-08-22 07:31 UTCGHSA enrichment
  10. 2026-08-21 23:49 UTCEPSS rescore
  11. 2026-08-21 04:41 UTCEG score recompute
  12. 2026-08-21 04:41 UTCGHSA enrichment
  13. 2026-08-20 22:55 UTCEPSS rescore
  14. 2026-08-20 04:54 UTCEG score recompute
  15. 2026-08-20 04:54 UTCGHSA enrichment
  16. 2026-08-19 17:04 UTCEPSS rescore
  17. 2026-08-18 22:56 UTCEG score recompute
  18. 2026-08-18 22:55 UTCGHSA enrichment
  19. 2026-08-18 13:48 UTCEPSS rescore
  20. 2026-08-17 23:43 UTCEG score recompute
  21. 2026-08-17 23:42 UTCGHSA enrichment
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-16 22:44 UTCEG score recompute
  24. 2026-08-16 22:44 UTCGHSA enrichment
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 75 more
  1. 2026-08-16 02:14 UTCEPSS rescore
  2. 2026-08-15 23:32 UTCEG score recompute
  3. 2026-08-15 23:32 UTCGHSA enrichment
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-15 00:19 UTCGHSA enrichment
  6. 2026-08-14 01:07 UTCEG score recompute
  7. 2026-08-14 01:07 UTCGHSA enrichment
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-13 01:54 UTCEG score recompute
  10. 2026-08-13 01:54 UTCGHSA enrichment
  11. 2026-08-12 13:51 UTCEPSS rescore
  12. 2026-08-12 02:42 UTCEG score recompute
  13. 2026-08-12 02:42 UTCGHSA enrichment
  14. 2026-08-11 03:29 UTCEG score recompute
  15. 2026-08-11 03:29 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 04:17 UTCEG score recompute
  18. 2026-08-10 04:17 UTCGHSA enrichment
  19. 2026-08-09 13:46 UTCEPSS rescore
  20. 2026-08-09 05:05 UTCEG score recompute
  21. 2026-08-09 05:05 UTCGHSA enrichment
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-08 05:53 UTCEG score recompute
  24. 2026-08-08 05:53 UTCGHSA enrichment
  25. 2026-08-07 06:41 UTCEG score recompute
  26. 2026-08-07 06:41 UTCGHSA enrichment
  27. 2026-08-06 13:47 UTCEPSS rescore
  28. 2026-08-06 07:29 UTCEG score recompute
  29. 2026-08-06 07:29 UTCGHSA enrichment
  30. 2026-08-05 19:17 UTCEPSS rescore
  31. 2026-08-05 08:16 UTCEG score recompute
  32. 2026-08-05 08:16 UTCGHSA enrichment
  33. 2026-08-04 15:10 UTCEPSS rescore
  34. 2026-08-04 10:39 UTCEPSS rescore
  35. 2026-08-04 09:05 UTCEG score recompute
  36. 2026-08-04 09:05 UTCGHSA enrichment
  37. 2026-08-03 10:36 UTCEPSS rescore
  38. 2026-08-03 09:50 UTCGHSA enrichment
  39. 2026-08-02 10:26 UTCEG score recompute
  40. 2026-08-02 10:26 UTCGHSA enrichment
  41. 2026-08-02 02:27 UTCEPSS rescore
  42. 2026-08-01 11:14 UTCEG score recompute
  43. 2026-08-01 11:14 UTCGHSA enrichment
  44. 2026-08-01 04:16 UTCEPSS rescore
  45. 2026-07-31 12:02 UTCEG score recompute
  46. 2026-07-31 12:02 UTCGHSA enrichment
  47. 2026-07-30 16:28 UTCEPSS rescore
  48. 2026-07-30 12:46 UTCEG score recompute
  49. 2026-07-30 12:46 UTCGHSA enrichment
  50. 2026-07-30 01:30 UTCEPSS rescore
  51. 2026-07-30 01:30 UTCEPSS rescore
  52. 2026-07-29 13:12 UTCEG score recompute
  53. 2026-07-29 13:12 UTCGHSA enrichment
  54. 2026-07-28 15:37 UTCEPSS rescore
  55. 2026-07-28 13:59 UTCEG score recompute
  56. 2026-07-28 13:59 UTCGHSA enrichment
  57. 2026-07-27 13:06 UTCEG score recompute
  58. 2026-07-27 13:06 UTCGHSA enrichment
  59. 2026-07-26 14:54 UTCEPSS rescore
  60. 2026-07-26 13:32 UTCEG score recompute
  61. 2026-07-26 13:32 UTCGHSA enrichment
  62. 2026-07-25 14:18 UTCEPSS rescore
  63. 2026-07-24 14:18 UTCEPSS rescore
  64. 2026-07-23 14:18 UTCEPSS rescore
  65. 2026-07-23 03:20 UTCEG score recompute
  66. 2026-07-22 14:08 UTCEPSS rescore
  67. 2026-07-21 15:25 UTCEPSS rescore
  68. 2026-07-20 17:08 UTCEPSS rescore
  69. 2026-07-19 14:31 UTCEPSS rescore
  70. 2026-07-19 14:31 UTCEPSS rescore
  71. 2026-07-18 10:04 UTCEPSS rescore
  72. 2026-07-16 17:03 UTCEPSS rescore
  73. 2026-07-16 13:39 UTCGHSA enrichment
  74. 2026-07-15 16:57 UTCEPSS rescore
  75. 2026-07-15 16:57 UTCEPSS rescore

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 0% probability of exploitation in the next 30 days, which ranks it in the top 92.5% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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