CVSS 4.0
1.3 lowCVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PCVE-2026-124329 flowci flow-core-x: Path traversal
Low (1.3) in flowci flow-core-x. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
On this page
A vulnerability was found in FlowCI flow-core-x up to 1.23.49. The impacted element is the function FileHelper.unzip of the file common/src/main/java/com/flowci/common/helper/FileHelper.java. The manipulation results in path traversal. The attack may be performed from remote. A high complexity level is associated with this attack. The exploitability is regarded as difficult. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.
Severity
CVSS 3.1
5.0 mediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L- EPSS
- 0.3% estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-11-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- Assigned by
- VulDB (CNA)
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-124329 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-124329?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-124329?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-124329 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-124329)
HTML:
<a href="https://cve.bz/cve/CVE-2026-124329"><img src="https://cve.bz/cve/badge/CVE-2026-124329.svg" alt="CVE-2026-124329"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| FlowCI flow-core-x | 1.23.0 |
| FlowCI flow-core-x | 1.23.1 |
| FlowCI flow-core-x | 1.23.2 |
| FlowCI flow-core-x | 1.23.3 |
| FlowCI flow-core-x | 1.23.4 |
| FlowCI flow-core-x | 1.23.5 |
| FlowCI flow-core-x | 1.23.6 |
| FlowCI flow-core-x | 1.23.7 |
| FlowCI flow-core-x | 1.23.8 |
| FlowCI flow-core-x | 1.23.9 |
| FlowCI flow-core-x | 1.23.10 |
| FlowCI flow-core-x | 1.23.11 |
| FlowCI flow-core-x | 1.23.12 |
| FlowCI flow-core-x | 1.23.13 |
| FlowCI flow-core-x | 1.23.14 |
| FlowCI flow-core-x | 1.23.15 |
| FlowCI flow-core-x | 1.23.16 |
| FlowCI flow-core-x | 1.23.17 |
| FlowCI flow-core-x | 1.23.18 |
| FlowCI flow-core-x | 1.23.19 |
| FlowCI flow-core-x | 1.23.20 |
| FlowCI flow-core-x | 1.23.21 |
| FlowCI flow-core-x | 1.23.22 |
| FlowCI flow-core-x | 1.23.23 |
| FlowCI flow-core-x | 1.23.24 |
| FlowCI flow-core-x | 1.23.25 |
| FlowCI flow-core-x | 1.23.26 |
| FlowCI flow-core-x | 1.23.27 |
| FlowCI flow-core-x | 1.23.28 |
| FlowCI flow-core-x | 1.23.29 |
| FlowCI flow-core-x | 1.23.30 |
| FlowCI flow-core-x | 1.23.31 |
| FlowCI flow-core-x | 1.23.32 |
| FlowCI flow-core-x | 1.23.33 |
| FlowCI flow-core-x | 1.23.34 |
| FlowCI flow-core-x | 1.23.35 |
| FlowCI flow-core-x | 1.23.36 |
| FlowCI flow-core-x | 1.23.37 |
| FlowCI flow-core-x | 1.23.38 |
| FlowCI flow-core-x | 1.23.39 |
| FlowCI flow-core-x | 1.23.40 |
| FlowCI flow-core-x | 1.23.41 |
| FlowCI flow-core-x | 1.23.42 |
| FlowCI flow-core-x | 1.23.43 |
| FlowCI flow-core-x | 1.23.44 |
| FlowCI flow-core-x | 1.23.45 |
| FlowCI flow-core-x | 1.23.46 |
| FlowCI flow-core-x | 1.23.47 |
| FlowCI flow-core-x | 1.23.48 |
| FlowCI flow-core-x | 1.23.49 |
Attack patterns (CAPEC)
- CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
- CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
- CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
- CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
- CAPEC-126 Path Traversal Likelihood: High · Severity: Very High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.