CVE-2026-56275

HIGHNVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory published 2026-06-23. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 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 server-side request forgery vulnerability in the Execute Flow node that allows attackers to bypass security validation by providing intranet addresses through the base URL field. Attackers can initiate HTTP requests to internal network addresses, access cloud metadata, and enumerate internal services by exploiting the missing secureFetch verification in httpSecurity.ts.

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
—
EPSS
8.2%
KEV
Not listed

Published

June 23, 2026

Last Modified

June 25, 2026

Advisory Details (2)

Auto-updated Jun 23, 2026
Patch available. Sources: github.
generic

Flowise - Server-Side Request Forgery via Execute Flow Base URL | Advisories | VulnCheck

https://www.vulncheck.com/advisories/flowise-server-side-request-forgery-via-execute-flow-base-url
github Patch Available

Flowise Execute Flow function has an SSRF vulnerability · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-9hrv-gvrv-6gf2

Vendor Advisories for CVE-2026-56275(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 9× in last 7d / 86× 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-07-22 14:08 UTCEPSS rescore
  2. 2026-07-20 17:08 UTCEPSS rescore
  3. 2026-07-19 14:31 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 02:29 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-17 03:33 UTCGHSA enrichment
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-16 14:31 UTCGHSA enrichment
  10. 2026-07-16 01:35 UTCGHSA enrichment
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 12:39 UTCGHSA enrichment
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-14 23:42 UTCGHSA enrichment
  17. 2026-07-14 10:17 UTCGHSA enrichment
  18. 2026-07-13 22:31 UTCEPSS rescore
  19. 2026-07-13 21:20 UTCGHSA enrichment
  20. 2026-07-13 08:23 UTCGHSA enrichment
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-12 19:25 UTCGHSA enrichment
  24. 2026-07-12 06:28 UTCGHSA enrichment
  25. 2026-07-12 05:46 UTCEPSS rescore
Show 61 more
  1. 2026-07-11 17:13 UTCGHSA enrichment
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-11 04:17 UTCGHSA enrichment
  5. 2026-07-10 15:16 UTCGHSA enrichment
  6. 2026-07-10 02:11 UTCGHSA enrichment
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-09 13:09 UTCGHSA enrichment
  10. 2026-07-09 00:12 UTCGHSA enrichment
  11. 2026-07-08 15:16 UTCEPSS rescore
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-08 11:16 UTCGHSA enrichment
  14. 2026-07-07 22:21 UTCGHSA enrichment
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-07 09:26 UTCGHSA enrichment
  18. 2026-07-06 20:28 UTCGHSA enrichment
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 07:17 UTCGHSA enrichment
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-06 02:23 UTCEPSS rescore
  24. 2026-07-05 18:13 UTCGHSA enrichment
  25. 2026-07-05 05:17 UTCGHSA enrichment
  26. 2026-07-05 02:31 UTCEPSS rescore
  27. 2026-07-05 02:30 UTCEPSS rescore
  28. 2026-07-04 15:56 UTCGHSA enrichment
  29. 2026-07-04 06:31 UTCEPSS rescore
  30. 2026-07-04 06:31 UTCEPSS rescore
  31. 2026-07-04 03:00 UTCGHSA enrichment
  32. 2026-07-03 14:01 UTCGHSA enrichment
  33. 2026-07-03 01:04 UTCGHSA enrichment
  34. 2026-07-02 12:09 UTCGHSA enrichment
  35. 2026-07-01 23:12 UTCGHSA enrichment
  36. 2026-07-01 15:07 UTCEPSS rescore
  37. 2026-07-01 10:17 UTCGHSA enrichment
  38. 2026-06-30 23:22 UTCEPSS rescore
  39. 2026-06-30 21:22 UTCGHSA enrichment
  40. 2026-06-30 08:26 UTCGHSA enrichment
  41. 2026-06-29 19:30 UTCGHSA enrichment
  42. 2026-06-29 14:06 UTCEPSS rescore
  43. 2026-06-29 14:06 UTCEPSS rescore
  44. 2026-06-29 06:35 UTCGHSA enrichment
  45. 2026-06-28 17:38 UTCGHSA enrichment
  46. 2026-06-28 14:07 UTCEPSS rescore
  47. 2026-06-28 04:56 UTCEPSS rescore
  48. 2026-06-28 04:56 UTCEPSS rescore
  49. 2026-06-28 04:42 UTCGHSA enrichment
  50. 2026-06-27 15:47 UTCGHSA enrichment
  51. 2026-06-27 03:08 UTCEPSS rescore
  52. 2026-06-27 02:51 UTCGHSA enrichment
  53. 2026-06-26 13:56 UTCEG score recompute▲ 1.10
  54. 2026-06-26 13:56 UTCGHSA enrichment
  55. 2026-06-25 19:49 UTCNVD updateCVSS v3 → 7.1 · severity → HIGH
  56. 2026-06-25 13:49 UTCEPSS rescore
  57. 2026-06-25 13:29 UTCGHSA enrichment
  58. 2026-06-24 14:05 UTCEPSS rescore
  59. 2026-06-24 13:06 UTCGHSA enrichment
  60. 2026-06-23 12:42 UTCEG score recompute
  61. 2026-06-23 12:40 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-56275?
CVE-2026-56275 is a high vulnerability published on June 23, 2026. Flowise before 3.1.0 contains a server-side request forgery vulnerability in the Execute Flow node that allows attackers to bypass security validation by providing intranet addresses through the base URL field. Attackers can initiate HTTP requests to internal network addresses, access cloud…
When was CVE-2026-56275 disclosed?
CVE-2026-56275 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56275 actively exploited?
CVE-2026-56275 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56275?
CVE-2026-56275 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-56275?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56275, 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-56275

Explore →

Is Your Infrastructure Affected by CVE-2026-56275?

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

Start Free Scan →Browse All CVEs