CVE-2026-56275

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM 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
Trending — 3 sources updated this week
7.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: 7.1Exploit: None knownExposed: 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(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
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 21× in last 7d / 101× 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 194 total refreshes for this CVE.

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

Related CVEs(same CWE)

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 0% probability of exploitation in the next 30 days, which ranks it in the top 76.3% of all scored CVEs.
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