How severe is CVE-2025-62233?

CVE-2025-62233 has a CVSS score of 6.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-62233?

CVE-2025-62233 affects the following packages: org.apache.dolphinscheduler:dolphinscheduler (Maven), org.apache.dolphinscheduler:dolphinscheduler-rpc (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-62233?

Update org.apache.dolphinscheduler:dolphinscheduler to 3.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-62233 is resolved across your whole dependency graph.

How do I detect CVE-2025-62233 in my Maven dependencies?

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.

How do I mitigate CVE-2025-62233 if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is CVE-2025-62233 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-62233 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-62233?

CVE-2025-62233 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-62233?

CVE-2025-62233 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-62233 published, and has it been updated?

CVE-2025-62233 was published on April 24, 2026 and was last updated on September 11, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2025-62233 — dolphinscheduler

MEDIUM

CVE-2025-62233 is a medium-severity (CVSS 6.3) Deserialization of Untrusted Data 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: Deserialization of untrusted data in RPC

Also known asGHSA-f786-9c63-8xr8

Published

Apr 24, 2026

Updated

Sep 11, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

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-62233.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2025-62233 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

☕org.apache.dolphinscheduler:dolphinscheduler☕org.apache.dolphinscheduler:dolphinscheduler-rpc

Real-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

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.dolphinscheduler:dolphinscheduler`	≥ 3.2.0&&< 3.3.1	3.3.1`org.apache.dolphinscheduler:dolphinscheduler:3.3.1`
☕Maven	`org.apache.dolphinscheduler:dolphinscheduler-rpc`	≥ 3.2.0&&< 3.3.1	3.3.1`org.apache.dolphinscheduler:dolphinscheduler-rpc:3.3.1`

Affected Products

1 product · 1 configurations

Application

dolphinschedulerapache

≥ 3.2.0 && < 3.3.1

range

Detection & mitigation playbook

Open-source dependency

Detect
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.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-62233 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2025-62233 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

Low

Raw vector

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

CWE Classification

CWE-502Deserialization of Untrusted Data

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Apr 24, 2026

Last updated

Sep 11, 2026

Identifiers

CVE-2025-62233

GHSA-f786-9c63-8xr8

References

Advisorygithub.com Advisorylists.apache.org Advisorynvd.nist.gov Webopenwall.com Webrepo.maven.apache.org Packagegithub.com

Related vulnerabilities

This CVE is medium severity; 7 of 8 other CVEs affecting dolphinscheduler are rated as high or higher (top: high).

CVE-2026-23902CVE-2025-62188CVE-2024-43115CVE-2024-43166CVE-2024-30188CVE-2024-29831CVE-2023-49250CVE-2023-51770

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedSep 11, 2026