Is org.apache.dolphinscheduler:dolphinscheduler 2.0 vulnerable?
Maven · 10 releases from 2.0.0 to 2.0.9 · latest org.apache.dolphinscheduler:dolphinscheduler is 3.4.3 · checked 18 Nov 2026
Yes: 9 known advisories
Yes. org.apache.dolphinscheduler:dolphinscheduler 2.0.9, the last 2.0 release, is affected by 9 known security advisories (1 critical, 5 high, 2 medium, 1 low), including CVE-2022-45875, CVE-2026-23902, CVE-2024-43115. 2 more affect earlier 2.0.x releases. Upgrade to 3.4.1 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=org.apache.dolphinscheduler:dolphinscheduler -DdepVersion=3.4.1 -DforceVersion=trueIs your project on an affected org.apache.dolphinscheduler:dolphinscheduler?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting org.apache.dolphinscheduler:dolphinscheduler 2.0.9
Apache DolphinScheduler has an Incorrect Authorization Vulnerability
- Affected
- <3.4.1
- Fixed in
- 3.4.1
Apache DolphinScheduler vulnerable to Alert Script Attack
- Affected
- <3.2.2
- Fixed in
- 3.2.2
Apache DolphinScheduler Incorrect Default Permissions Vulnerability
- Affected
- <3.3.1
- Fixed in
- 3.3.1
Apache DolphinScheduler: RCE by arbitrary js execution
- Affected
- <3.2.2
- Fixed in
- 3.2.2
Improper Certificate Validation in Apache DolphinScheduler
- Affected
- <3.2.1
- Fixed in
- 3.2.1
Arbitrary File Read Vulnerability in Apache Dolphinscheduler
- Affected
- <3.2.1
- Fixed in
- 3.2.1
Session Fixation Apache DolphinScheduler
- Affected
- >=1.3.8 <3.2.1
- Fixed in
- 3.2.1
Apache DolphinScheduler vulnerable to Improper Input Validation
- Affected
- <3.0.2 · >=3.1.0 <3.1.1
- Fixed in
- 3.0.2, 3.1.1
Apache DolphinScheduler vulnerable to Path Traversal
- Affected
- <3.0.0
- Fixed in
- 3.0.0
Fixed within 2.0.x, affecting earlier releases
Apache DolphinScheduler vulnerable to Path Traversal
- Affected
- <2.0.6
- Fixed in
- 2.0.6
Uncontrolled Resource Consumption in Apache DolphinScheduler
- Affected
- <2.0.5
- Fixed in
- 2.0.5
Every org.apache.dolphinscheduler:dolphinscheduler 2.0.x release
Affected: 2.0.0 to 2.0.9. Latest org.apache.dolphinscheduler:dolphinscheduler: 3.4.3.
| Version | Known advisories |
|---|---|
| org.apache.dolphinscheduler:dolphinscheduler 2.0.9 | CVE-2026-23902, CVE-2024-43115, CVE-2024-43166, CVE-2024-29831, CVE-2023-49250, CVE-2023-51770, CVE-2023-50270, CVE-2022-45875, CVE-2022-34662 |
| org.apache.dolphinscheduler:dolphinscheduler 2.0.8 | CVE-2026-23902, CVE-2024-43115, CVE-2024-43166, CVE-2024-29831, CVE-2023-49250, CVE-2023-51770, CVE-2023-50270, CVE-2022-45875, CVE-2022-34662 |
| org.apache.dolphinscheduler:dolphinscheduler 2.0.7 | CVE-2026-23902, CVE-2024-43115, CVE-2024-43166, CVE-2024-29831, CVE-2023-49250, CVE-2023-51770, CVE-2023-50270, CVE-2022-45875, CVE-2022-34662 |
| org.apache.dolphinscheduler:dolphinscheduler 2.0.6 | CVE-2026-23902, CVE-2024-43115, CVE-2024-43166, CVE-2024-29831, CVE-2023-49250, CVE-2023-51770, CVE-2023-50270, CVE-2022-45875, CVE-2022-34662 |
| org.apache.dolphinscheduler:dolphinscheduler 2.0.5 | CVE-2026-23902, CVE-2024-43115, CVE-2024-43166, CVE-2024-29831, CVE-2023-49250, CVE-2023-51770, CVE-2023-50270, CVE-2022-45875, CVE-2022-34662, CVE-2022-26884 |
| org.apache.dolphinscheduler:dolphinscheduler 2.0.4 | CVE-2026-23902, CVE-2024-43115, CVE-2024-43166, CVE-2024-29831, CVE-2023-49250, CVE-2023-51770, CVE-2023-50270, CVE-2022-45875, CVE-2022-34662, CVE-2022-26884, CVE-2022-25598 |
| org.apache.dolphinscheduler:dolphinscheduler 2.0.3 | CVE-2026-23902, CVE-2024-43115, CVE-2024-43166, CVE-2024-29831, CVE-2023-49250, CVE-2023-51770, CVE-2023-50270, CVE-2022-45875, CVE-2022-34662, CVE-2022-26884, CVE-2022-25598 |
| org.apache.dolphinscheduler:dolphinscheduler 2.0.2 | CVE-2026-23902, CVE-2024-43115, CVE-2024-43166, CVE-2024-29831, CVE-2023-49250, CVE-2023-51770, CVE-2023-50270, CVE-2022-45875, CVE-2022-34662, CVE-2022-26884, CVE-2022-25598 |
| org.apache.dolphinscheduler:dolphinscheduler 2.0.1 | CVE-2026-23902, CVE-2024-43115, CVE-2024-43166, CVE-2024-29831, CVE-2023-49250, CVE-2023-51770, CVE-2023-50270, CVE-2022-45875, CVE-2022-34662, CVE-2022-26884, CVE-2022-25598 |
| org.apache.dolphinscheduler:dolphinscheduler 2.0.0 | CVE-2026-23902, CVE-2024-43115, CVE-2024-43166, CVE-2024-29831, CVE-2023-49250, CVE-2023-51770, CVE-2023-50270, CVE-2022-45875, CVE-2022-34662, CVE-2022-26884, CVE-2022-25598 |
Which of your client projects are still on org.apache.dolphinscheduler:dolphinscheduler 2.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.apache.dolphinscheduler:dolphinscheduler version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.apache.dolphinscheduler:dolphinscheduler versions
- org.apache.dolphinscheduler:dolphinscheduler 3.2
- org.apache.dolphinscheduler:dolphinscheduler 3.1
- org.apache.dolphinscheduler:dolphinscheduler 3.0
- org.apache.dolphinscheduler:dolphinscheduler 1.3
- org.apache.dolphinscheduler:dolphinscheduler 1.2
- org.apache.dolphinscheduler:dolphinscheduler 3.4
- org.apache.dolphinscheduler:dolphinscheduler 3.3
- All org.apache.dolphinscheduler:dolphinscheduler advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.