Apache DolphinScheduler vulnerable to Path TraversalGHSA-fp35-xrrr-3gph
MEDIUMGHSA-fp35-xrrr-3gph is a medium-severity (CVSS 6.5) Path Traversal vulnerability in org.apache.dolphinscheduler:dolphinscheduler. A fix is available for org.apache.dolphinscheduler:dolphinscheduler — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-fp35-xrrr-3gph.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.dolphinscheduler:dolphinschedulerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
When users add resources to the resource center with a relation path, this vulnerability will cause path traversal issues for logged-in users. Users should upgrade to version 3.0.0 to avoid this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.dolphinscheduler:dolphinscheduler | all versions | 3.0.0org.apache.dolphinscheduler:dolphinscheduler:3.0.0 |
Affected Products
dolphinschedulerapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.dolphinscheduler:dolphinscheduler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.dolphinscheduler:dolphinscheduler to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fp35-xrrr-3gph is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is GHSA-fp35-xrrr-3gph in your dependencies?
Find it across Maven, including transitive dependencies.