Is org.apache.dolphinscheduler:dolphinscheduler 3.4 vulnerable?

Maven · 4 releases from 3.4.0 to 3.4.3 · latest org.apache.dolphinscheduler:dolphinscheduler is 3.4.3 · checked 18 Nov 2026

No known advisories in the last release

org.apache.dolphinscheduler:dolphinscheduler 3.4.3, the last 3.4 release, has no known advisories. 1 advisory affects earlier 3.4.x releases, so update to 3.4.3.

Update within 3.4:mvn versions:use-dep-version -Dincludes=org.apache.dolphinscheduler:dolphinscheduler -DdepVersion=3.4.3 -DforceVersion=true

Is your project on an affected org.apache.dolphinscheduler:dolphinscheduler?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 3.4.x, affecting earlier releases

  • HighCVE-2026-23902GHSA-72mv-wwvm-vgp524 Apr 2026

    Apache DolphinScheduler has an Incorrect Authorization Vulnerability

    Affected
    <3.4.1
    Fixed in
    3.4.1

Every org.apache.dolphinscheduler:dolphinscheduler 3.4.x release

Affected: 3.4.0. 3.4.1 and later are not affected.

VersionKnown advisories
org.apache.dolphinscheduler:dolphinscheduler 3.4.3None
org.apache.dolphinscheduler:dolphinscheduler 3.4.2None
org.apache.dolphinscheduler:dolphinscheduler 3.4.1None
org.apache.dolphinscheduler:dolphinscheduler 3.4.0CVE-2026-23902

Which of your client projects are still on org.apache.dolphinscheduler:dolphinscheduler 3.4?

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

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.