PatchSiren

PatchSiren cyber security CVE debrief

CVE-2025-62233 Apache Software Foundation CVE debrief

CVE-2025-62233: Apache DolphinScheduler Deserialization of Untrusted Data Vulnerability. This issue affects Apache DolphinScheduler versions >= 3.2.0 and < 3.3.1, allowing attackers with access to Master or Worker nodes to compromise the system by creating a StandardRpcRequest with a malicious class type and sending RPC requests. Defenders should assess exposure and prioritize upgrading to version 3.3.1 or later to prevent potential system compromise and data breaches. The vulnerability is a Deserialization of Untrusted Data issue in the RPC module, which can lead to elevation of privileges and possible data breaches.

Vendor
Apache Software Foundation
Product
Apache DolphinScheduler
CVSS
MEDIUM 6.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-04-24
Original CVE updated
2026-09-30
Advisory published
2026-04-24
Advisory updated
2026-09-30

Who should care

Defenders responsible for Apache DolphinScheduler deployments, particularly those with versions >= 3.2.0 and < 3.3.1, should assess exposure and prioritize upgrading to version 3.3.1 or later.

Why it matters

CVE-2025-62233 is a Deserialization of Untrusted Data vulnerability in Apache DolphinScheduler that allows attackers to compromise the system. Defenders should assess exposure, prioritize upgrading to version 3.3.1 or later, and monitor RPC requests to prevent potential system compromise and data breaches.

  • Potential system compromise through malicious RPC requests
  • Elevation of privileges through deserialization of untrusted data
  • Possible data breaches or unauthorized access

Technical summary

The CVE record and NVD entry describe a Deserialization of Untrusted Data vulnerability in Apache DolphinScheduler's RPC module. The vulnerability affects versions >= 3.2.0 and < 3.3.1. An attacker with access to Master or Worker nodes can create a StandardRpcRequest with a malicious class type and send RPC requests to compromise the system. This issue can lead to potential system compromise, elevation of privileges, and possible data breaches. Defenders should assess exposure and prioritize upgrading to version 3.3.1 or later.

Defensive priority

Medium

Recommended defensive actions

  • Upgrade to Apache DolphinScheduler version 3.3.1 or later
  • Restrict access to Master and Worker nodes
  • Monitor RPC requests to DolphinScheduler Master/Worker nodes
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the Deserialization of Untrusted Data vulnerability in Apache DolphinScheduler. The vulnerability affects versions >= 3.2.0 and < 3.3.1. Attackers with access to Master or Worker nodes can compromise the system by creating a StandardRpcRequest with a malicious class type.

Sources and references

Verified primary and authoritative sources

  • CVE-2025-62233 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2025-62233

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2025-62233 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2025-62233

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.