CVE-2026-70476

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.5% (42nd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.2Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, several organization billing endpoints in packages/server/src/enterprise/routes/organization.route.ts and packages/server/src/enterprise/controllers/organization.controller.ts accept attacker-controlled Stripe subscriptionId values without verifying that the identifier belongs to the authenticated user's organization. An authenticated attacker can perform unauthorized Stripe subscription operations on other tenants, including changing subscription plans or modifying seat quantities, resulting in financial impact and service disruption. This issue is fixed in 3.1.3.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
53
EG Risk 53/100CISA SSVC

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
Severity82% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 4, 2026

Last Modified

September 11, 2026

Advisory Details (4)

Auto-updated Aug 4, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github_commit, github_release, github.
github_commit Patch Available

commit 4d7899d02ca3 (FlowiseAI/Flowise)

Patch available: FlowiseAI/Flowise [email protected] (contains commit 4d7899d02ca3)

https://github.com/FlowiseAI/Flowise/commit/4d7899d02ca370a5510406be5c91483085a412f9
github_pr Patch Available

fix: flowise-310

Patch available: FlowiseAI/Flowise [email protected] (PR #6321 merged 2026-05-08)

https://github.com/FlowiseAI/Flowise/pull/6321
github Patch Available🟡 PoC Available

Broken Access Control in Stripe Subscription Endpoints Allows Cross-Tenant Billing Manipulation · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-gmmw-qg98-6j6p

Vendor Advisories for CVE-2026-70476(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 rangeFix by version rangeDependents
flowise—
  • every version up to 3.1.3: fixed in 3.1.3
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 50× 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 112 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-70476?
CVE-2026-70476 is a high vulnerability published on August 4, 2026. Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, several organization billing endpoints in packages/server/src/enterprise/routes/organization.route.ts and packages/server/src/enterprise/controllers/organization.controller.ts accept…
When was CVE-2026-70476 disclosed?
CVE-2026-70476 was first published on August 4, 2026, with the most recent update on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-70476 actively exploited?
CVE-2026-70476 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-70476?
CVE-2026-70476 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-70476?
A fix for CVE-2026-70476 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-70476 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-70476

Explore →

Is Your Infrastructure Affected by CVE-2026-70476?

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