Quick answers
- Is CVE-2026-47340 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47340 being exploited in the wild.
- How severe is CVE-2026-47340?
- Medium severity, with a CVSS score of 6.5, published 17 June 2026.
- Which products and versions are affected?
- Apache Software Foundation DolphinScheduler < 3.4.2, before 3.4.2; org.apache.dolphinscheduler:dolphinscheduler-api (Maven) < 3.4.2, ECOSYSTEM:introduced=0,fixed=3.4.2.
- Is there a fix for CVE-2026-47340?
- Yes. org.apache.dolphinscheduler:dolphinscheduler-api (Maven): upgrade to 3.4.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47340 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-47340?
- Check whether you run Apache Software Foundation DolphinScheduler or org.apache.dolphinscheduler:dolphinscheduler-api (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- org.apache.dolphinscheduler:dolphinscheduler-api (Maven): upgrade to 3.4.2 or later
# set org.apache.dolphinscheduler:dolphinscheduler-api to 3.4.2 in your pom.xml or build.gradle
Technical details
An incorrect authorization vulnerability (CWE-200) exists in the Apache DolphinScheduler API. The root cause is a failure to properly validate user permissions when requesting alert instances, allowing an authenticated user to bypass intended access controls and view alerts associated with unauthorized alert groups. The attack is reachable over the network and requires low-privileged authentication but no user interaction. This vulnerability is resolved in version 3.4.2.
Affected products
- Apache Software Foundation DolphinScheduler < 3.4.2
Identifiers
- CVE-2026-47340
- GHSA-694g-j8pj-cjj5
Timeline
- 2026-06-17: disclosed
- 2026-06-17: advisory
- 2026-06-17: patched: Fixed in version 3.4.2