CVE-2026-73603

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-08-13. NVD baseline CVSS 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this weekElevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: Elevated riskExposed: 0

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

Flowise before 3.1.4 fails to validate chatflow visibility in the unauthenticated text-to-speech endpoint, allowing attackers to abuse private chatflow TTS credentials. Unauthenticated attackers can generate unlimited text-to-speech audio using stored OpenAI or ElevenLabs API keys by providing a valid chatflow UUID, incurring costs on the chatflow owner's account.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
55(Attend)
EG Risk 55/100SSVC: Attend

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
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

August 13, 2026

Last Modified

September 4, 2026

Advisory Details (2)

Auto-updated Aug 13, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Flowise before 3.1.4 Credential Abuse via Text-to-Speech | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flowise-before-credential-abuse-via-text-to-speech
github Patch Available🟡 PoC Available

Unauthenticated Credential Abuse via Text-to-Speech Endpoint Allows Unauthorized Use of Private Chatflow TTS Credentials · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-8gj2-2cvc-6xx7

Vendor Advisories for CVE-2026-73603(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
flowise3.1.4

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 78× 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 105 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-73603?
CVE-2026-73603 is a medium vulnerability published on August 13, 2026. Flowise before 3.1.4 fails to validate chatflow visibility in the unauthenticated text-to-speech endpoint, allowing attackers to abuse private chatflow TTS credentials. Unauthenticated attackers can generate unlimited text-to-speech audio using stored OpenAI or ElevenLabs API keys by providing a…
When was CVE-2026-73603 disclosed?
CVE-2026-73603 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73603 actively exploited?
CVE-2026-73603 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 72.7% of all scored CVEs.
What is the CVSS score of CVE-2026-73603?
CVE-2026-73603 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-73603?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73603, 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-73603

Explore →

Is Your Infrastructure Affected by CVE-2026-73603?

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