dbcve.org
DolphinschedulerApplication · Apache

CVE-2026-42357

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
Incorrect Authorization vulnerability allows users to access workflow instance information belonging to projects they do not have permission to access. This issue affects Apache DolphinScheduler versions prior to 3.4.2. Users are recommended to upgrade to version 3.4.2, which fixes this 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 incorrect authorization (broken access control) vulnerability in Apache DolphinScheduler where authenticated users can bypass project-level permission checks to access workflow instance information for projects they do not have permission to access. The authorization logic in the workflow instance retrieval functionality fails to properly validate user permissions against project access controls.

MitigationUpgrade to Apache DolphinScheduler version 3.4.2 which contains the corrected authorization logic to enforce project-level access controls.

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. Check the installed Apache DolphinScheduler version
    Identify the version of Apache DolphinScheduler currently running in your environment. This is typically visible in the application UI footer, startup logs, or system information endpoints.
    Affected if The installed version is any release prior to 3.4.2
  2. Confirm workflow instance retrieval is accessible
    Determine if the workflow instance retrieval functionality is enabled and accessible to authenticated users. This feature allows users to query workflow execution records.
    Affected if Authenticated users can access workflow instance data through API or UI endpoints
  3. Verify project-level permission enforcement
    Using an authenticated test account without project access, attempt to retrieve workflow instance information for a project the account is not authorized to view. Compare the actual response against expected access denial.
    Affected if The system returns workflow instance data for projects the user has not been granted permission to access

Your environment is affected if the installed Apache DolphinScheduler version is below 3.4.2 and authenticated users can access workflow instance details for projects they have not been explicitly permitted 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 corrected authorization logic to enforce project-level access controls.

Recommended fix High confidence

3.4.2

  1. Review the Apache DolphinScheduler upgrade documentation for your current version
  2. Backup your existing DolphinScheduler database and configuration files
  3. Download Apache DolphinScheduler version 3.4.2 from the official Apache download mirrors
  4. Stop the running DolphinScheduler services
  5. Execute the database migration scripts provided in the 3.4.2 release
  6. Upgrade DolphinScheduler binaries to version 3.4.2
  7. Update configuration files to match any new requirements in 3.4.2
  8. Start DolphinScheduler services and verify they start correctly
Caveat Check release notes for any configuration or API changes between your current version and 3.4.2

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

Fix this in Dolphinscheduler Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42357 — 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-42357 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