CVE-2026-69257

HIGHPre-NVD 7.67.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% 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, secondary
Elevated
7.6EG
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.6Exploit: Elevated riskExposed: 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.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
7.6
EG Score
7.6(medium)
EG Risk
50(Track*)
EG Risk 50/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
Severity76% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 4, 2026

Advisory Details (4)

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

[email protected]

Patch available: FlowiseAI/Flowise [email protected]

https://github.com/FlowiseAI/Flowise/releases/tag/[email protected]
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 rangeFixed inDependents
flowise—3.1.3—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 35× 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-08-21 02:18 UTCEG score recompute
  2. 2026-08-20 22:56 UTCEPSS rescore
  3. 2026-08-20 03:53 UTCEG score recompute
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-18 18:17 UTCEG score recompute
  6. 2026-08-18 13:49 UTCEPSS rescore
  7. 2026-08-18 13:49 UTCEPSS rescore
  8. 2026-08-17 19:34 UTCEG score recompute
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 19:57 UTCEG score recompute
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 08:47 UTCEG score recompute
  14. 2026-08-16 02:15 UTCEPSS rescore
  15. 2026-08-15 10:27 UTCEG score recompute
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 00:58 UTCEG score recompute
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-12 15:28 UTCEG score recompute
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-11 16:59 UTCEG score recompute
  22. 2026-08-11 05:49 UTCEG score recompute
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-09 20:21 UTCEG score recompute
  25. 2026-08-09 13:47 UTCEPSS rescore
Show 10 more
  1. 2026-08-08 22:02 UTCEG score recompute
  2. 2026-08-08 16:37 UTCEPSS rescore
  3. 2026-08-07 23:42 UTCEG score recompute
  4. 2026-08-06 03:03 UTCEG score recompute
  5. 2026-08-05 19:17 UTCEPSS rescore
  6. 2026-08-05 19:17 UTCEPSS rescore
  7. 2026-08-04 17:23 UTCEG score recompute
  8. 2026-08-04 17:07 UTCEG score recompute▲ 7.60
  9. 2026-08-04 17:06 UTCMITRE cvelistV5CVSS v3 → 7.6 · CVSS v4 → 7.6
  10. 2026-08-04 16:07 UTCEG score recompute

Related CVEs(same CWE)

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 in the National Vulnerability Database on August 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-69257 actively exploited?
CVE-2026-69257 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 83.8% of all scored CVEs.
What is the CVSS score of CVE-2026-69257?
CVE-2026-69257 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-69257?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69257, 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-69257

Explore →

Is Your Infrastructure Affected by CVE-2026-69257?

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

Start Free Scan →Browse All CVEs