dbcve.org
DolphinschedulerApplication · Apache

CVE-2026-23902

HIGH · 8.1 CVSS v3.1 Published 2026-04-24
Fix available
A fix is available. Upgrade to 3.4.1 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Incorrect Authorization vulnerability in Apache DolphinScheduler allows authenticated users with system login permissions to use tenants that are not defined on the platform during workflow execution. This issue affects Apache DolphinScheduler versions prior to 3.4.1.  Users are recommended to upgrade to version 3.4.1, which fixes this issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Incorrect authorization vulnerability in Apache DolphinScheduler allows authenticated users with system login permissions to use tenants that are not defined on the platform during workflow execution. This bypasses proper tenant validation controls in the authorization layer.

MitigationUpgrade to Apache DolphinScheduler version 3.4.1 or later which contains the fix for this authorization bypass.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DolphinschedulerApplication
Affected:< 3.4.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify DolphinScheduler installation and version
    Check the running DolphinScheduler version by reviewing the deployed JAR files, Docker image tags, or the application's about/info endpoint. Common paths: /opt/dolphinscheduler directory, or docker container inspection.
    Affected if The installed version is earlier than 3.4.1 (e.g., 3.3.x, 3.2.x, or earlier releases)
  2. Confirm tenant feature is in use
    Log into the DolphinScheduler web UI and navigate to the Tenant Management section. Review whether any tenants are defined and whether workflow resources are assigned to specific tenants.
    Affected if Tenants are defined and workflows are being assigned to or executed using those tenants
  3. Verify tenant validation in authorization settings
    Review the security configuration in DolphinScheduler: navigate to Security -> Permission Settings or Tenant Authorization. Check if there are tenant-to-user mappings defined.
    Affected if Tenant-to-user mappings exist and users can potentially select any tenant during workflow definition
  4. Inspect workflow definitions for tenant assignments
    Query the database or use the API to list workflow definitions and their associated tenants. Check the tenant_id field in the t_ds_process_definition table or equivalent.
    Affected if Workflows are assigned to tenants that may not have been properly validated during creation

A user is affected if DolphinScheduler version is below 3.4.1 AND the tenant feature is actively used, allowing authenticated users to potentially assign unvalidated tenants to workflows.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.4.1 or later
Fixed in 3.4.1
Interim mitigation

Upgrade to Apache DolphinScheduler version 3.4.1 or later which contains the fix for this authorization bypass.

Recommended fix High confidence

3.4.1

  1. Backup the current DolphinScheduler database and configuration files
  2. Stop the running DolphinScheduler service
  3. Download Apache DolphinScheduler version 3.4.1 from the official Apache release repository
  4. Review the upgrade documentation for version 3.4.1 for any specific migration steps
  5. Execute the database upgrade scripts provided in the 3.4.1 release (if any)
  6. Deploy the new 3.4.1 binaries to your installation directories
  7. Start the DolphinScheduler service
  8. Verify the service is running correctly and tenants are properly validated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dolphinscheduler Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23902 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-23902 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data