CVE-2026-69257

HIGHNVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under NVD CVSS v3. EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). 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
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.6Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, Flowise's HTTP security module httpSecurity.ts did not normalize IPv4-mapped IPv6 addresses such as ::ffff:127.0.0.1 and ::ffff:169.254.169.254 before checking them against the deny list. Because ipaddr.js reports these addresses as ipv6 while IPv4 CIDR deny-list entries are ipv4, isDeniedIP() skipped the IPv4 CIDR checks. An attacker who controls DNS resolution for a hostname used by the HTTP Node, API Chain, Document Loader, MCP tool, or other paths using secureAxiosRequest(), secureFetch(), or checkDenyList() could return a AAAA record for an IPv4-mapped target and cause requests to reach localhost, internal services, or cloud metadata endpoints. This issue is fixed in version 3.1.3.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
55
EG Risk 55/100CISA SSVC

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
Severity86% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 4, 2026

Last Modified

September 14, 2026

Advisory Details (4)

Auto-updated Aug 4, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_commit Patch Available

commit 0fc769208395 (FlowiseAI/Flowise)

Patch available: FlowiseAI/Flowise [email protected] (contains commit 0fc769208395)

https://github.com/FlowiseAI/Flowise/commit/0fc769208395641c1411ccdb9c81416e54802155
github_pr Patch Available

Fix FLOWISE 453

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

https://github.com/FlowiseAI/Flowise/pull/6431
github Patch Available🟡 PoC Available

SSRF Protection Bypass via IPv4-Mapped IPv6 Addresses in Flowise · Advisory · FlowiseAI/Flowise · GitHub

Affected: v3.0.13

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-c6xh-wv4j-ppv5

Vendor Advisories for CVE-2026-69257(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 rangeFix by version rangeDependents
flowise—
  • every version up to 3.1.3: fixed in 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 / 47× 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 106 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-69257?
CVE-2026-69257 is a high 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, Flowise's HTTP security module httpSecurity.ts did not normalize IPv4-mapped IPv6 addresses such as ::ffff:127.0.0.1 and ::ffff:169.254.169.254 before checking them against the deny list.…
When was CVE-2026-69257 disclosed?
CVE-2026-69257 was first published 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-69257 actively exploited?
CVE-2026-69257 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69257?
CVE-2026-69257 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-69257?
A fix for CVE-2026-69257 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-69257 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69257

Explore →

Is Your Infrastructure Affected by CVE-2026-69257?

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