dbcve.org
DolphinschedulerApplication · Apache

CVE-2025-62233

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-24
Fix available
A fix is available. Upgrade to 3.3.1 or later.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
Deserialization of Untrusted Data vulnerability in Apache DolphinScheduler RPC module. This issue affects Apache DolphinScheduler:  Version >= 3.2.0 and < 3.3.1. Attackers who can access the Master or Worker nodes can compromise the system by creating a StandardRpcRequest, injecting a malicious class type into it, and sending RPC requests to the DolphinScheduler Master/Worker nodes. Users are recommended to upgrade to version [3.3.1], which fixes the issue.

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

Deserialization of Untrusted Data vulnerability in Apache DolphinScheduler's RPC module allows attackers with access to Master or Worker nodes to inject malicious class types into StandardRpcRequest objects, potentially achieving arbitrary code execution during deserialization.

MitigationUpgrade Apache DolphinScheduler to version 3.3.1 or later. Until then, restrict network access to Master/Worker RPC ports to limit exposure.

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.2.0, < 3.3.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Identify installed DolphinScheduler version
    Run 'dsctl version' or check the version file in the DolphinScheduler installation directory, or inspect the UI footer for the version number
    Affected if Version is 3.2.0 through 3.3.0 (anything >= 3.2.0 but < 3.3.1)
  2. Confirm Master or Worker services are running
    Check running processes for Master or Worker roles, or review the deployed cluster topology configuration
    Affected if Master or Worker nodes are deployed and running
  3. Verify RPC port exposure
    Check network configuration or firewall rules for RPC ports (default 5678 for Master, 1234 for Worker) and determine if they accept external connections
    Affected if RPC ports are accessible from untrusted networks or non-admin users
  4. Inspect RPC module configuration
    Review the dolphinscheduler-rpc module configuration in the deployment config files or check if the RPC endpoint is enabled in the Master/Worker configuration
    Affected if RPC module is enabled and StandardRpcRequest handling is active

You are affected if your DolphinScheduler version is 3.2.0 to 3.3.0, you have Master or Worker nodes running, and those RPC ports are accessible to attackers.

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.3.1 or later
Fixed in 3.3.1
Interim mitigation

Upgrade Apache DolphinScheduler to version 3.3.1 or later. Until then, restrict network access to Master/Worker RPC ports to limit exposure.

Recommended fix High confidence

3.3.1

  1. Back up current DolphinScheduler data and configuration files
  2. Stop all DolphinScheduler services (Master and Worker nodes)
  3. Download Apache DolphinScheduler version 3.3.1 from the official Apache repository
  4. Install or upgrade to version 3.3.1 on all Master and Worker nodes
  5. Verify configuration files are intact after upgrade
  6. Start DolphinScheduler services in the correct order (Master first, then Worker)
  7. Verify the installation by checking service status and logs

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
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62233 — 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-62233 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