CVE-2026-69258

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 61% of all CVEs by exploit prediction. 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
Trending — 3 sources updated this weekElevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: Elevated riskExposed: 0

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

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, the unauthenticated POST /api/v1/prediction/:id endpoint accepted an overrideConfig object and unconditionally spread it into internal flowConfig and flowData objects in packages/server/src/utils/buildChatflow.ts and packages/server/src/utils/index.ts without checking apiOverrideStatus. This allowed unauthenticated attackers to inject arbitrary properties into the flow execution context of any public chatflow, overwrite values such as chatId, sessionId, and chatHistory, and control values resolved through $flow.* template variables consumed by flow nodes. This issue is fixed in version 3.1.3.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
72(Attend)
EG Risk 72/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
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

August 4, 2026

Last Modified

September 14, 2026

Advisory Details (4)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

Unauthenticated Property Injection into Flow Execution Context via Ungated `overrideConfig` Spread in Prediction API · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-6vh2-wg4h-4vwj
github_release Patch Available

[email protected]

Patch available: FlowiseAI/Flowise [email protected]

https://github.com/FlowiseAI/Flowise/releases/tag/[email protected]
github_pr Patch Available

bugfix:308 | remove ungated overrideConfig spread

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

https://github.com/FlowiseAI/Flowise/pull/6279
github_commit Patch Available

commit 23b997ee5ef9 (FlowiseAI/Flowise)

Patch available: FlowiseAI/Flowise [email protected] (contains commit 23b997ee5ef9)

https://github.com/FlowiseAI/Flowise/commit/23b997ee5ef9e269b628bad0f56f1ecb86bd2fca

Vendor Advisories for CVE-2026-69258(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.3—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× 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.

  1. 2026-09-18 23:12 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 01:08 UTCEG score recompute
  4. 2026-09-17 01:11 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 11:14 UTCEG score recompute
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 06:56 UTCEG score recompute
  9. 2026-09-14 19:54 UTCEG score recompute▲ 0.30
  10. 2026-09-14 19:52 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  11. 2026-09-14 01:54 UTCEG score recompute
  12. 2026-09-13 02:18 UTCEG score recompute
  13. 2026-09-12 02:41 UTCEG score recompute
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 14:52 UTCEG score recompute
  16. 2026-09-11 09:37 UTCEPSS rescore
  17. 2026-09-10 14:56 UTCEG score recompute
  18. 2026-09-09 08:51 UTCEG score recompute
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-07 18:34 UTCEG score recompute
  21. 2026-09-07 16:01 UTCEPSS rescore
  22. 2026-09-06 18:16 UTCEG score recompute
  23. 2026-09-06 13:47 UTCEPSS rescore
  24. 2026-09-05 18:33 UTCEG score recompute
  25. 2026-09-05 15:31 UTCEPSS rescore
Show 61 more
  1. 2026-09-05 04:09 UTCEG score recompute
  2. 2026-09-04 10:08 UTCEG score recompute
  3. 2026-09-04 05:07 UTCEPSS rescore
  4. 2026-09-03 07:29 UTCEG score recompute
  5. 2026-09-02 14:12 UTCEPSS rescore
  6. 2026-09-01 20:49 UTCEG score recompute
  7. 2026-09-01 13:54 UTCEPSS rescore
  8. 2026-08-30 21:47 UTCEG score recompute
  9. 2026-08-30 19:17 UTCEPSS rescore
  10. 2026-08-30 09:59 UTCEG score recompute
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-29 21:47 UTCEG score recompute
  13. 2026-08-28 21:42 UTCEPSS rescore
  14. 2026-08-27 20:44 UTCEG score recompute
  15. 2026-08-26 19:59 UTCEG score recompute
  16. 2026-08-26 14:47 UTCEPSS rescore
  17. 2026-08-25 20:22 UTCEG score recompute
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-24 20:46 UTCEG score recompute
  20. 2026-08-23 09:22 UTCEG score recompute
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-22 09:46 UTCEG score recompute
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-21 10:10 UTCEG score recompute
  25. 2026-08-20 22:56 UTCEPSS rescore
  26. 2026-08-19 22:46 UTCEG score recompute
  27. 2026-08-19 17:04 UTCEPSS rescore
  28. 2026-08-18 23:10 UTCEG score recompute
  29. 2026-08-18 13:49 UTCEPSS rescore
  30. 2026-08-18 13:49 UTCEPSS rescore
  31. 2026-08-17 23:34 UTCEG score recompute
  32. 2026-08-17 13:47 UTCEPSS rescore
  33. 2026-08-16 23:57 UTCEG score recompute
  34. 2026-08-16 14:56 UTCEPSS rescore
  35. 2026-08-16 14:56 UTCEPSS rescore
  36. 2026-08-16 12:08 UTCEG score recompute
  37. 2026-08-16 02:15 UTCEPSS rescore
  38. 2026-08-15 12:33 UTCEG score recompute
  39. 2026-08-15 01:30 UTCEPSS rescore
  40. 2026-08-14 01:08 UTCEG score recompute
  41. 2026-08-13 22:00 UTCEPSS rescore
  42. 2026-08-13 01:32 UTCEG score recompute
  43. 2026-08-12 13:51 UTCEPSS rescore
  44. 2026-08-11 14:08 UTCEG score recompute
  45. 2026-08-11 02:20 UTCEG score recompute
  46. 2026-08-11 00:00 UTCEPSS rescore
  47. 2026-08-09 14:55 UTCEG score recompute
  48. 2026-08-09 13:47 UTCEPSS rescore
  49. 2026-08-09 03:08 UTCEG score recompute
  50. 2026-08-08 16:37 UTCEPSS rescore
  51. 2026-08-08 03:32 UTCEG score recompute
  52. 2026-08-06 16:08 UTCEG score recompute
  53. 2026-08-06 13:47 UTCEPSS rescore
  54. 2026-08-06 04:20 UTCEG score recompute
  55. 2026-08-05 19:17 UTCEPSS rescore
  56. 2026-08-05 19:17 UTCEPSS rescore
  57. 2026-08-05 16:32 UTCEG score recompute
  58. 2026-08-05 15:29 UTCEG score recompute
  59. 2026-08-04 17:23 UTCEG score recompute▲ 8.80
  60. 2026-08-04 17:23 UTCNVD updateCVSS v3 → 8.8 · CVSS v4 → 8.8
  61. 2026-08-04 16:07 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-69258?
CVE-2026-69258 is a critical 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, the unauthenticated POST /api/v1/prediction/:id endpoint accepted an overrideConfig object and unconditionally spread it into internal flowConfig and flowData objects in…
When was CVE-2026-69258 disclosed?
CVE-2026-69258 was first published in the National Vulnerability Database on August 4, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69258 actively exploited?
CVE-2026-69258 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 61.4% of all scored CVEs.
What is the CVSS score of CVE-2026-69258?
CVE-2026-69258 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-69258?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69258, 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-69258

Explore →

Is Your Infrastructure Affected by CVE-2026-69258?

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

Start Free Scan →Browse All CVEs