CVE-2026-56273

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2026-07-08. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.5Exploit: 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.0 contains a path traversal vulnerability in Faiss and SimpleStore vector store implementations that accept unsanitized basePath parameters from authenticated users. Attackers with valid API tokens can write vector store data to arbitrary filesystem locations, potentially enabling code execution or data exfiltration.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
45(Track)
EG Risk 45/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%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 9, 2026

Advisory Details (2)

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

Flowise - Path Traversal in Vector Store basePath Parameter | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flowise-path-traversal-in-vector-store-basepath-parameter
github Patch Available🟡 PoC Available

Path Traversal in Vector Store basePath · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-w6v6-49gh-mc9w

Vendor Advisories for CVE-2026-56273(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

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 19× in last 7d / 79× 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 116 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56273?
CVE-2026-56273 is a medium vulnerability published on July 8, 2026. Flowise before 3.1.0 contains a path traversal vulnerability in Faiss and SimpleStore vector store implementations that accept unsanitized basePath parameters from authenticated users. Attackers with valid API tokens can write vector store data to arbitrary filesystem locations, potentially…
When was CVE-2026-56273 disclosed?
CVE-2026-56273 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56273 actively exploited?
CVE-2026-56273 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 59.4% of all scored CVEs.
What is the CVSS score of CVE-2026-56273?
CVE-2026-56273 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-56273?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56273, 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-56273

Explore →

Is Your Infrastructure Affected by CVE-2026-56273?

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

Start Free Scan →Browse All CVEs