Apache DolphinScheduler RPC module has a Deserialization of Untrusted Data vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2025-62233: 0.54% estimated exploitation activity in the next 30 days; percentile 45.29 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

24 Apr 2026, 12:30 UTC

Last modified by the source

5 May 2026, 00:06 UTC

Source last checked

26 Oct 2026, 16:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f786-9c63-8xr8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-62233

Advisory: Apache DolphinScheduler RPC module has a Deserialization of Untrusted Data vulnerability
IDs: CVE-2025-62233, GHSA-f786-9c63-8xr8
Record: https://patchnext.com/advisories/cve-2025-62233 (revision 1, source checked 26 Oct 2026, 16:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.dolphinscheduler:dolphinscheduler-rpc 3.3.1; org.apache.dolphinscheduler:dolphinscheduler 3.3.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.dolphinscheduler:dolphinscheduler-rpc: affected >= 3.2.0, < 3.3.1; fixed in 3.3.1
- Maven org.apache.dolphinscheduler:dolphinscheduler: affected >= 3.2.0, < 3.3.1; fixed in 3.3.1

## Suggested inspection (read-only)
- Maven org.apache.dolphinscheduler:dolphinscheduler-rpc: check the installed version with your package manager.
- Maven org.apache.dolphinscheduler:dolphinscheduler: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.dolphinscheduler:dolphinscheduler-rpc, org.apache.dolphinscheduler:dolphinscheduler.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-f786-9c63-8xr8 (GitHub-reviewed advisory GHSA-f786-9c63-8xr8 lists affected ranges: Maven org.apache.dolphinscheduler:dolphinscheduler >=3.2.0 =3.2.0 <3.3.1)

Commands are suggestions: review each one before running it.