Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
CRITICAL severity

CVE-2020-11974 — dolphinscheduler

CRITICAL

CVE-2020-11974 is a critical-severity (CVSS 9.8) remote code execution vulnerability in org.apache.dolphinscheduler:dolphinscheduler. A fix is available for org.apache.dolphinscheduler:dolphinscheduler — see the affected versions and patch details below.

Remote code execution in DolphinScheduler

Also known asGHSA-jpj4-5xwp-cv23
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
8.1%probability of exploitation in next 30 days
Lower Risk+0.33%
Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk
6.46%8.57%10.7%12.8%11.6%8.1%Apr 26Jul 26Oct 26

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

How urgent is this, really

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

Where this sits among everything scored

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

Real-World Exposure

1 pkg affected
☕org.apache.dolphinscheduler:dolphinscheduler

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

In DolphinScheduler 1.2.0 and 1.2.1, with mysql connectorj a remote code execution vulnerability exists when choosing mysql as database.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.dolphinscheduler:dolphinschedulerall versions1.3.0org.apache.dolphinscheduler:dolphinscheduler:1.3.0

Affected Products

1 product · 2 configurations
Application
dolphinschedulerapache
2 versions
1.2.01.2.1

Detection & mitigation playbook

Open-source dependency

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

  2. Fix

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

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

Frequently Asked Questions

In DolphinScheduler 1.2.0 and 1.2.1, with mysql connectorj a remote code execution vulnerability exists when choosing mysql as database.
O3 Security · Impact-Aware SCA

Is CVE-2020-11974 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-11974: dolphinscheduler RCE — Fixed in 1.3.0