CVE-2026-66082: Apache DolphinScheduler: Cross-project authorization bypasses in DolphinScheduler API (schedule / workflow）

Q: Who can exploit this issue?

An attacker must be authenticated and have the required permissions in at least one DolphinScheduler project. They can then use that project's projectCode with a schedule, workflow-definition, or task-instance identifier belonging to another project.

Q: Are all DolphinScheduler deployments affected by default?

The issue affects Apache DolphinScheduler versions before 3.4.3. Exploitation depends on having an authenticated user account with the relevant permissions in a project and knowledge of target resource identifiers in another project.

Q: What could an attacker do with a successful bypass?

They can activate or deactivate workflow schedules in another project and change workflow definitions between ONLINE and OFFLINE states. This can alter workflow availability and interfere with task execution across project boundaries.

Q: What should teams do to remediate this vulnerability?

Upgrade Apache DolphinScheduler to version 3.4.3, which fixes the issue. The provided information does not specify an alternative mitigation for environments that cannot upgrade immediately.

Published Oct 8, 2026

Updated

An authorization bypass vulnerability in Apache DolphinScheduler allows authenticated users to perform unauthorized operations on workflow schedules, workflow definitions, and task instances in other projects.

The affected endpoints check permissions against the supplied projectCode but fail to verify that the target resource belongs to that project. An authenticated user with the required permissions in one project can supply that project's code together with a resource identifier from another project, bypassing the target project's access restrictions.

The affected endpoints include:

POST /projects/{projectCode}/schedules/{id}/online and /offline: Activate or deactivate workflow schedules in another project.

POST /projects/{projectCode}/workflow-definition/{code}/release: Change the ONLINE/OFFLINE state of workflow definitions in another project.

Successful exploitation allows users to alter workflow availability and interfere with task execution in projects they are not authorized to access.

This issue affects Apache DolphinScheduler: before 3.4.3.

Users are recommended to upgrade to version 3.4.3, which fixes the issue.

Affected Software

1 affected component

Apache Dolphinscheduler<3.4.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade Apache DolphinScheduler to a version that resolves this vulnerability.
Fixed in 3.4.3

Event History

Oct 8, 2026

CVE Published

via MITRE·08:16 AM

Data Sourced

via MITRE·08:16 AM

DescriptionWeakness

Data Sourced

via NVD·09:16 AM

DescriptionWeakness

Frequently Asked Questions

Who can exploit this issue?

An attacker must be authenticated and have the required permissions in at least one DolphinScheduler project. They can then use that project's projectCode with a schedule, workflow-definition, or task-instance identifier belonging to another project.

Are all DolphinScheduler deployments affected by default?

The issue affects Apache DolphinScheduler versions before 3.4.3. Exploitation depends on having an authenticated user account with the relevant permissions in a project and knowledge of target resource identifiers in another project.

What could an attacker do with a successful bypass?

They can activate or deactivate workflow schedules in another project and change workflow definitions between ONLINE and OFFLINE states. This can alter workflow availability and interfere with task execution across project boundaries.

What should teams do to remediate this vulnerability?

Upgrade Apache DolphinScheduler to version 3.4.3, which fixes the issue. The provided information does not specify an alternative mitigation for environments that cannot upgrade immediately.

CVE-2026-66082: Apache DolphinScheduler: Cross-project authorization bypasses in DolphinScheduler API (schedule / workflow）

Affected Software

Remediation

Event History

Frequently Asked Questions

Who can exploit this issue?

Are all DolphinScheduler deployments affected by default?

What could an attacker do with a successful bypass?

What should teams do to remediate this vulnerability?

Company

Resources

Contact

Frequently Asked Questions

Who can exploit this issue?

Are all DolphinScheduler deployments affected by default?

What could an attacker do with a successful bypass?

What should teams do to remediate this vulnerability?