CVE-2025-62188 — dolphinscheduler
HIGHCVE-2025-62188 is a high-severity (CVSS 7.5) Information Exposure vulnerability in org.apache.dolphinscheduler:dolphinscheduler. A fix is available for org.apache.dolphinscheduler:dolphinscheduler — see the affected versions and patch details below.
Apache DolphinScheduler: Users can access sensitive information through the actuator endpoint.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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 CVE-2025-62188.
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
An Exposure of Sensitive Information to an Unauthorized Actor vulnerability exists in Apache DolphinScheduler.
This vulnerability may allow unauthorized actors to access sensitive information, including database credentials.
This issue affects Apache DolphinScheduler versions 3.1.*.
Users are recommended to upgrade to:
- version ≥ 3.2.0 if using 3.1.x
As a temporary workaround, users who cannot upgrade immediately may restrict the exposed management endpoints by setting the following environment variable:
MANAGEMENT_ENDPOINTS_WEB_EXPOSURE_INCLUDE=health,metrics,prometheus
Alternatively, add the following configuration to the application.yaml file:
management:
endpoints:
web:
exposure:
include: health,metrics,prometheus
This issue has been reported as CVE-2023-48796:
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.dolphinscheduler:dolphinscheduler | ≥ 3.1.0&&< 3.2.0 | 3.2.0org.apache.dolphinscheduler:dolphinscheduler:3.2.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.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-62188 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2025-62188 in your dependencies?
Find it across Maven, including transitive dependencies.