Incorrect Default Permissions in Apache DolphinSchedulerGHSA-qhh5-9738-g9mx
MEDIUMFix: apache/incubator-dolphinscheduler@b8a9e2eGHSA-qhh5-9738-g9mx is a medium-severity (CVSS 6.5) CWE-264 vulnerability in org.apache.dolphinscheduler:dolphinscheduler-api. A fix is available for org.apache.dolphinscheduler:dolphinscheduler-api — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-qhh5-9738-g9mx by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.apache.dolphinscheduler:dolphinscheduler-apiReal-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
Versions of Apache DolphinScheduler prior to 1.3.2 allowed an ordinary user under any tenant to override another users password through the API interface.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.dolphinscheduler:dolphinscheduler-api | all versions | 1.3.2org.apache.dolphinscheduler:dolphinscheduler-api:1.3.2 |
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-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.dolphinscheduler:dolphinscheduler-api to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qhh5-9738-g9mx is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is GHSA-qhh5-9738-g9mx in your dependencies?
Find it across Maven, including transitive dependencies.