Security Deep Dive
Flowise
Security posture and CVE patch evidence from tracked releases.
1 actively-exploited dependency CVE affects [email protected].
KEV-listed CVEs are confirmed exploited in the wild — patch urgently.
Versions by Severity
CVEs are attributed to tracked releases published before the patch release.
| Version | Published | C | H | M | L | KEV | Notes |
|---|---|---|---|---|---|---|---|
| [email protected] | 2026-06-25 | — | — | — | — | — |
Latest
Patches
CVE-2025-31125
|
| [email protected] | 2026-04-14 | — | — | 1 | — | KEV 1 |
—
|
| [email protected] | 2026-03-23 | — | — | 1 | — | KEV 1 |
—
|
| [email protected] | 2026-03-16 | — | — | 1 | — | KEV 1 |
—
|
| [email protected] | 2026-02-03 | — | — | 1 | — | KEV 1 |
—
|
| [email protected] | 2025-12-05 | — | — | 1 | — | KEV 1 |
—
|
| [email protected] | 2025-11-16 | — | — | 1 | — | KEV 1 |
—
|
| [email protected] | 2025-11-06 | — | — | 1 | — | KEV 1 |
—
|
| [email protected] | 2025-10-08 | — | — | 1 | — | KEV 1 |
—
|
| [email protected] | 2025-09-15 | — | — | 1 | — | KEV 1 |
—
|
| [email protected] | 2025-09-15 | — | — | 1 | — | KEV 1 |
—
|
| [email protected] | 2025-08-11 | — | — | 1 | — | KEV 1 |
—
|
| [email protected] | 2025-07-11 | — | — | 1 | — | KEV 1 |
—
|
| [email protected] | 2025-06-27 | — | — | 1 | — | KEV 1 |
—
|
| [email protected] | 2025-06-12 | — | — | 1 | — | KEV 1 |
—
|
Trust Signals — 3 of 9 Present
Evidence already collected from releases and repository metadata.
Security Score
A composite score aggregating Scorecard performance, CVE patch history, OpenSSF badge tier, and dependency vulnerability exposure. Score ≥ 7.0 is healthy; < 4.0 warrants attention.
epss
0.25 / 0.5
Max EPSS 0.588
freshness
1.00 / 1.0
2d stale
scorecard
2.00 / 4.0
⚠ Estimated — not yet collected
cve health
0.00 / 2.5
⚠ No direct scan — 18c/85h transitive CVEs
patch speed
0.50 / 0.5
⚠ Estimated — no CVE patch history
kev exposure
-1.50 / 1.5
KEV exposure detected
supply chain risk
-1.50 / 10.0
Risk 100.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
0.0
10%
Provenance trust
provenance trust
5.0
40%
Maintainer health
maintainer health
10.0
10%
Operational risk
operational risk
1.5
10%
How is this calculated?
The six dimensions group the legacy score signals into weighted categories: direct vulnerability status, patch responsiveness, dependency exposure, provenance checks, maintainer activity, and exploitability risk. The flat component values above remain available for compatibility.
Supply Chain Risk
Risk 100.0/100OpenSSF Badge
Badge indicates adherence to open-source best practices.
CVE Patch History
Tracks CVEs that were addressed in tagged releases. Shorter gap between disclosure and patch = faster response. EPSS = predicted probability of exploitation in next 30 days (FIRST.org); colored at ≥90%ile and ≥50%ile.
CVEs Patched by Year
| CVE | Severity | EPSS | Disclosed | Fixed in | Days to fix | vs Ecosystem Median | KEV |
|---|---|---|---|---|---|---|---|
| CVE-2025-31125 | MEDIUM | 99%ile | — | [email protected] | — | — | KEV |
KEV = CISA Known Exploited Vulnerabilities catalog — actively exploited in the wild.
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
18
High
85
Medium
105
Low
22
Unknown
0
1 dependency vulnerabilities are in KEV.
CISA confirmed these vulnerabilities are actively exploited. Treat as critical priority.
Showing 230 of 230