Is org.apache.dolphinscheduler:dolphinscheduler 3.3 vulnerable?

Maven · 2 releases from 3.3.1 to 3.3.2 · latest org.apache.dolphinscheduler:dolphinscheduler is 3.4.3 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. org.apache.dolphinscheduler:dolphinscheduler 3.3.2, the last 3.3 release, is affected by 1 known security advisory (1 high), including CVE-2026-23902. Upgrade to 3.4.1 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=org.apache.dolphinscheduler:dolphinscheduler -DdepVersion=3.4.1 -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

Advisories affecting org.apache.dolphinscheduler:dolphinscheduler 3.3.2

  • 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.3.x release

Affected: 3.3.1 to 3.3.2. Latest org.apache.dolphinscheduler:dolphinscheduler: 3.4.3.

VersionKnown advisories
org.apache.dolphinscheduler:dolphinscheduler 3.3.2CVE-2026-23902
org.apache.dolphinscheduler:dolphinscheduler 3.3.1CVE-2026-23902

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

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.