CVE-2026-66082 Apache Software Foundation CVE debrief

Who should care

Administrators and users of Apache DolphinScheduler, especially those with multi-project setups, should assess exposure and upgrade to version 3.4.3 or later. They should also review access controls, monitor for suspicious activity, and verify project access restrictions.

Why it matters

Authenticated users can bypass project access restrictions, allowing unauthorized operations on workflow schedules and definitions. Defenders should upgrade to version 3.4.3, review access controls, and monitor for suspicious activity.

• Potential unauthorized changes to workflow availability
• Interference with task execution in unauthorized projects
• Need for verification of project access restrictions
• Potential for lateral movement within multi-project environments

Technical summary

The vulnerability allows authenticated users to bypass access restrictions and perform unauthorized operations on workflow schedules, definitions, and task instances in other projects. This is possible due to insufficient verification of project codes in the affected endpoints. The affected endpoints include POST /projects/{projectCode}/schedules/{id}/online and /offline, and POST /projects/{projectCode}/workflow-definition/{code}/release. Successful exploitation allows users to alter workflow availability and interfere with task execution in projects they are not authorized to access.

Defensive priority

Upgrade to version 3.4.3 or later to fix the issue.

Recommended defensive actions

• Upgrade Apache DolphinScheduler to version 3.4.3 or later
• Review and restrict access to workflow schedules, definitions, and task instances
• Monitor for unauthorized operations in projects
• Verify project access restrictions and review access controls
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including affected versions and potential impacts. The vulnerability is caused by insufficient verification of project codes in the affected endpoints, allowing authenticated users to bypass access restrictions. Defenders should verify project access restrictions, review access controls, and monitor for suspicious activity.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.