How severe is GHSA-f786-9c63-8xr8?

GHSA-f786-9c63-8xr8 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 GHSA-f786-9c63-8xr8?

GHSA-f786-9c63-8xr8 affects the following packages: org.apache.dolphinscheduler:dolphinscheduler (Maven), org.apache.dolphinscheduler:dolphinscheduler-rpc (Maven). Ecosystems affected: Maven.

How do I fix GHSA-f786-9c63-8xr8?

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 GHSA-f786-9c63-8xr8 is resolved across your whole dependency graph.

How do I detect GHSA-f786-9c63-8xr8 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.dolphinscheduler:dolphinscheduler. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-f786-9c63-8xr8 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-f786-9c63-8xr8?

O3 pinpoints whether GHSA-f786-9c63-8xr8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-f786-9c63-8xr8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-f786-9c63-8xr8 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.

When was GHSA-f786-9c63-8xr8 published, and has it been updated?

GHSA-f786-9c63-8xr8 was published on April 24, 2026 and was last updated on May 5, 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

GHSA-f786-9c63-8xr8

MEDIUM

GHSA-f786-9c63-8xr8 is a medium-severity (CVSS 6.3) remote code execution vulnerability in org.apache.dolphinscheduler:dolphinscheduler. O3 Security confirms whether GHSA-f786-9c63-8xr8 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Apache DolphinScheduler RPC module has a Deserialization of Untrusted Data vulnerability

Also known asCVE-2025-62233

Published

Apr 24, 2026

Updated

May 5, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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
☕Maven	`org.apache.dolphinscheduler:dolphinscheduler-rpc`	≥ 3.2.0&&< 3.3.1	3.3.1

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-f786-9c63-8xr8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-f786-9c63-8xr8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-f786-9c63-8xr8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 GHSA-f786-9c63-8xr8 in your dependencies?

O3 detects GHSA-f786-9c63-8xr8 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works