CVE-2024-43166: Apache DolphinScheduler · Incorrect Default Permissions
Affects Apache DolphinSchedulerSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.2.2 as a priority.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.2.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade org.apache.dolphinscheduler/dolphinscheduler to 3.2.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavenorg.apache.dolphinscheduler/dolphinschedulerpkg:maven/org.apache.dolphinscheduler/dolphinschedulerOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediate upgrade of Apache DolphinScheduler to version 3.3.1 or later is essential to remediate the incorrect default permissions issue. 2. Conduct a thorough audit of current DolphinScheduler deployments focusing on permission settings, access controls, and user roles to ensure no overly permissive configurations remain. 3. Implement network segmentation and firewall rules to restrict access to DolphinScheduler management interfaces to trusted internal IPs only. 4. Enable and monitor detailed logging and alerting for unusual access patterns or unauthorized attempts to interact with the scheduler. 5. Employ application-layer security controls such as Web Application Firewalls (WAFs) to detect and block exploitation attempts. 6. Regularly review and update security policies related to workflow orchestration tools and integrate vulnerability scanning into CI/CD pipelines to catch outdated versions. 7. Educate system administrators and DevOps teams about the risks associated with default permissions and the importance of secure configuration management.
Description
Incorrect Default Permissions vulnerability in Apache DolphinScheduler. This issue affects Apache DolphinScheduler: before 3.2.2. Users are recommended to upgrade to version 3.3.1, which fixes the issue.