dbcve.org
DolphinschedulerApplication · Apache

CVE-2025-62188

HIGH · 7.5 CVSS v3.1 Published 2026-04-09
Fix available
A fix is available. Upgrade to 3.2.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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: https://cveprocess.apache.org/cve5/CVE-2023-48796

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache DolphinScheduler 3.1.x exposes management endpoints that allow unauthorized actors to access sensitive information, including database credentials. This is a sensitive information exposure vulnerability where the Spring Boot management endpoints are overly exposed without proper access controls.

MitigationUpgrade to version 3.2.0 or later, or restrict management endpoints by setting MANAGEMENT_ENDPOINTS_WEB_EXPOSURE_INCLUDE=health,metrics,prometheus in environment or configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DolphinschedulerApplication
Affected:>= 3.1.0, < 3.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed DolphinScheduler version
    Run 'dolphinscheduler-version.sh' or inspect the version file in the DolphinScheduler installation directory, or query the API endpoint /actuator/info if accessible
    Affected if Version is 3.1.x (>= 3.1.0 and < 3.2.0)
  2. Verify management endpoints are accessible
    Attempt to access common Spring Boot actuator endpoints such as /actuator/env, /actuator/configprops, /actuator/heapdump, or /actuator/beans via HTTP request to the DolphinScheduler host
    Affected if Any of these endpoints return HTTP 200 with sensitive configuration or environment data without authentication
  3. Check current endpoint exposure configuration
    Inspect the DolphinScheduler configuration files (application.yaml or application.properties) or environment variables for MANAGEMENT_ENDPOINTS_WEB_EXPOSURE_INCLUDE or MANAGEMENT_ENDPOINTS_WEB_EXPOSURE_EXCLUDE settings
    Affected if The configuration either does not exist or includes wildcard '*' or sensitive endpoints like env, configprops, dump, heapdump are not explicitly excluded
  4. Confirm database credentials are exposed
    Access /actuator/env endpoint and search for properties containing 'spring.datasource' or 'DATASOURCE' keywords in the response
    Affected if Database usernames, passwords, or connection strings are visible in plain text in the actuator endpoint response

You are affected if running DolphinScheduler 3.1.0 through 3.1.x AND management actuator endpoints are accessible without authentication, exposing sensitive environment or configuration data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.2.0 or later
Fixed in 3.2.0
Interim mitigation

Upgrade to version 3.2.0 or later, or restrict management endpoints by setting MANAGEMENT_ENDPOINTS_WEB_EXPOSURE_INCLUDE=health,metrics,prometheus in environment or configuration.

Recommended fix High confidence

3.2.0 or later

  1. 1. Review the DolphinScheduler 3.2.0 release notes and migration guide for any breaking changes
  2. 2. Create a full backup of your current DolphinScheduler database and configuration files
  3. 3. Stop all DolphinScheduler services (API server, master, worker, alert)
  4. 4. Upgrade DolphinScheduler to version 3.2.0 or later by updating your deployment artifacts (Docker images, Helm charts, or installation packages)
  5. 5. Run any database migration scripts if required by the 3.2.0 release
  6. 6. Start the upgraded DolphinScheduler services
  7. 7. Verify the vulnerability is resolved by confirming management endpoints no longer expose sensitive information
  8. 8. Test that normal DolphinScheduler functionality (workflow execution, alerts, etc.) works as expected
Caveat Review 3.2.0 release notes for breaking changes; may require database migration and configuration adjustments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dolphinscheduler Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62188 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-62188 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data