VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

apache-dolphinscheduler: vulnerability history, versions and safety

apache-dolphinscheduler is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 32 releases, from Jan 2021 to Nov 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded U4
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all apache-dolphinscheduler vulnerabilities

Vulert verdict on apache-dolphinscheduler 4.1.0 i

Updated on 23 Oct 2026

Careful: 4.1.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 4.1.0 — affected i
  • Vulnerabilities on record 4 over 2 years · 0 in the last year i
  • Latest disclosure 24 Nov 2023 i
  • Highest CVSS 7.5 i
  • With no published fix 1 i
  • Stars 72 i
  • Last release 21 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for apache-dolphinscheduler, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.1.0 12 Jan 2025 U1 Apache-2.0 No Details →
4.0.4 12 Oct 2023 U1 Apache-2.0 No Details →
4.0.2a12 19 Sep 2023 U1 Apache-2.0 No Details →
4.0.2a11 18 Jul 2023 U1 Apache-2.0 No Details →
4.0.2a10 13 Jul 2023 U1 Apache-2.0 No Details →
4.0.2a9 13 Jul 2023 U1 Apache-2.0 No Details →
4.0.3 14 Apr 2023 U1 Apache-2.0 No Details →
4.0.2.1 23 Mar 2023 U1 Apache-2.0 No Details →
4.0.2 23 Mar 2023 U1 Apache-2.0 No Details →
4.0.2a8 22 Mar 2023 U1 Apache-2.0 No Details →
4.0.2a7 14 Mar 2023 U1 Apache-2.0 No Details →
4.0.2a6 05 Mar 2023 U1 Apache-2.0 No Details →
4.0.2a5 28 Feb 2023 U1 Apache-2.0 No Details →
4.0.2a4 27 Feb 2023 U1 Apache-2.0 No Details →
4.0.1 25 Feb 2023 U1 Apache-2.0 No Details →
4.0.2a3 12 Feb 2023 U1 Apache-2.0 No Details →
4.0.2a2 06 Feb 2023 U1 Apache-2.0 No Details →
4.0.2a1 06 Feb 2023 U1 Apache-2.0 No Details →
3.0.2 10 Jan 2023 U1 Apache-2.0 No Details →
4.0.0 21 Dec 2022 U1 Apache-2.0 No Details →
3.1.1 11 Nov 2022 U1 Apache-2.0 No Details →
2.0.7 25 Oct 2022 U2 Apache-2.0 No Details →
3.1.0 30 Sep 2022 U1 Apache-2.0 No Details →
3.0.1 27 Sep 2022 U3 Apache-2.0 No Details →
3.0.0 08 Aug 2022 U3 Apache-2.0 No Details →
3.0.0b2 04 Jul 2022 U2 Apache-2.0 No Details →
3.0.0b1 31 May 2022 U2 Apache-2.0 No Details →
3.0.0a0 06 May 2022 U2 Apache-2.0 No Details →
2.0.5.1 07 Mar 2022 U2 Apache-2.0 No Details →
2.0.5 07 Mar 2022 U2 Apache-2.0 No Details →
0.1.1 28 Jan 2022 U3 Apache-2.0 No Details →
0.1.0 28 Jan 2022 U3 Apache-2.0 No Details →

All 32 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 1
  • 2023 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for apache-dolphinscheduler

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-48796: Apache DolphinScheduler Sensitive Information Exposure Vulnerability 7.5 high 3.0.2 24 Nov 2023
CVE-2020-13922: Apache DolphinScheduler Password Override Vulnerability 6.5 medium No fix published 11 Jan 2021
CVE-2022-25598: Apache DolphinScheduler Regular express Denial of Service (ReDoS) Vulnerability N/A unrated 2.0.5 30 Mar 2022
CVE-2022-45875: Remote Command Execution Vulnerability in Apache DolphinScheduler N/A unrated 3.0.2 04 Jan 2023

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About apache-dolphinscheduler

Is apache-dolphinscheduler safe to use?

Vulert records 4 vulnerabilities for apache-dolphinscheduler in PyPI: 0 critical, 0 high, 0 medium and 0 low, plus 4 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is apache-dolphinscheduler's Vulert package health score?

Vulert scores apache-dolphinscheduler 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of apache-dolphinscheduler affected?

Yes. 4.1.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of apache-dolphinscheduler should I use?

4.1.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does apache-dolphinscheduler have?

4 vulnerabilities are recorded for apache-dolphinscheduler in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 4 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new apache-dolphinscheduler vulnerabilities disclosed?

0 vulnerabilities were recorded for apache-dolphinscheduler in the last 12 months, and the oldest entry in this database dates to 11 Jan 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of apache-dolphinscheduler are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor apache-dolphinscheduler for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the apache-dolphinscheduler version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.