Skip to content
VulniPulse
Advisory severityMedium4.3Apache Software Foundation

Medium [CVE-2026-81569] Apache DolphinScheduler: improper authorization vulnerability exists in the handling of sub-workflow tasks

This medium-severity Apache Software Foundation advisory covers CVE-2026-81569 affecting Apache DolphinScheduler.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-81569 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Apache Software FoundationUnclassified
Open source advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

An improper authorization vulnerability exists in the handling of sub-workflow tasks. An authenticated user who does not have permission to access a target project can reference and invoke a workflow belonging to that project through a sub-workflow task.

The system does not properly verify whether the user has permission to execute the referenced workflow or access its project. As a result, the user can bypass project-level authorization controls and cause workflows in unauthorized projects to be executed.

Successful exploitation may allow unauthorized execution of workflow tasks and access to the resources or data available to the target workflow.

This issue affects Apache DolphinScheduler: before 3.4.3.

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

Affected versions
  • Apache DolphinScheduler before 3.4.3

Official advisory · high-confidence parse· fetched 7 days ago·verify at source

Fixed versions
  • 3.4.3

Official advisory · high-confidence parse· fetched 7 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Users are recommended to upgrade to version 3.4.3, which fixes the issue.

Official advisory · high-confidence parse· fetched 7 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.