CVE-2026-41274

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 54% 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
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 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.0, the GraphCypherQAChain node forwards user-provided input directly into the Cypher query execution pipeline without proper sanitization. An attacker can inject arbitrary Cypher commands that are executed on the underlying Neo4j database, enabling data exfiltration, modification, or deletion. This vulnerability is fixed in 3.1.0.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
39.6%
KEV
Not listed

Published

April 23, 2026

Last Modified

May 4, 2026

Advisory Details (1)

Auto-updated May 12, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Cypher Injection in GraphCypherQAChain · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-28g4-38q8-3cwc

Affected Packages

(2 across 1 ecosystem)
npm(2)
PackageVulnerable rangeFixed inDependents
flowise—3.1.0—
flowise-components—3.1.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 42× 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 143 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-41274?
CVE-2026-41274 is a critical vulnerability published on April 23, 2026. Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, the GraphCypherQAChain node forwards user-provided input directly into the Cypher query execution pipeline without proper sanitization. An attacker can inject arbitrary Cypher commands that are…
When was CVE-2026-41274 disclosed?
CVE-2026-41274 was first published in the National Vulnerability Database on April 23, 2026, with the most recent update on May 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-41274 actively exploited?
CVE-2026-41274 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41274?
CVE-2026-41274 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-41274?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41274, 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-41274

Explore →

Is Your Infrastructure Affected by CVE-2026-41274?

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

Start Free Scan →Browse All CVEs