dbcve.org
DolphinschedulerApplication · Apache

CVE-2026-47340

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to 3.4.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Allow authenticated users to access alert instances associated with alert groups they do not have permission to access. in Apache DolphinScheduler. This issue affects Apache DolphinScheduler: before 3.4.2. Users are recommended to upgrade to version 3.4.2, which fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an broken access control vulnerability in Apache DolphinScheduler where authenticated users can access alert instances belonging to alert groups they do not have permission to view. The application fails to properly validate user permissions before returning alert instance data, allowing privilege escalation through unauthorized access to sensitive alert configurations.

MitigationUpgrade to Apache DolphinScheduler version 3.4.2 which contains the authorization fix for this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DolphinschedulerApplication
Affected:< 3.4.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache DolphinScheduler version
    Locate the version file or check through the admin UI. Common locations: check the about/page in the UI, or look for a version file in the installation directory. Alternatively, check the startup logs which typically display the version on boot.
    Affected if The installed version is any version prior to 3.4.2 (e.g., 3.4.1, 3.4.0, 3.3.x, 3.2.x, earlier releases).
  2. Confirm alert groups are configured
    Navigate to the Alert Groups management section in the DolphinScheduler UI or check the alert_group table in the database if direct database access is available. Verify that alert groups exist in the system.
    Affected if Alert groups are defined and active in the installation.
  3. Review user permissions on alert groups
    Access the Resources > Alert Group Permissions section or the User Management area. Examine which users are assigned to which alert groups. Look for users who have general system access (are authenticated) but are not explicitly granted permissions to specific alert groups.
    Affected if There are authenticated users in the system who do not have explicit permission grants to all existing alert groups.
  4. Test cross-group alert instance access
    Using a user account that has system login access but limited or no alert group permissions, attempt to query or view alert instances through API endpoints or UI. Check if alert instances from groups the user is not assigned to are returned in any API responses or displayed in any views.
    Affected if Alert instance data from groups the test user is not permissions for is returned or accessible.

You are affected if running Apache DolphinScheduler version below 3.4.2 AND alert groups exist in the system where some authenticated users can access alert instances from groups they have not been granted permission to view.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.4.2 or later
Fixed in 3.4.2
Interim mitigation

Upgrade to Apache DolphinScheduler version 3.4.2 which contains the authorization fix for this vulnerability.

Recommended fix High confidence

3.4.2

  1. 1. Back up your current DolphinScheduler installation including database and configuration files
  2. 2. Download Apache DolphinScheduler version 3.4.2 from the official Apache distribution repository
  3. 3. Review the official upgrade documentation for your specific deployment method (Kubernetes, Docker, or standalone)
  4. 4. Execute the upgrade procedure following the documented steps for your installation type
  5. 5. Verify that the upgrade completed successfully by checking the version number in the UI or via CLI
  6. 6. Test that alert group permissions are now properly enforced - users should only see alert instances for groups they have permission to access

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dolphinscheduler Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47340 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47340 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data