dbcve.org
DolphinschedulerApplication · Apache

CVE-2026-32967

CRITICAL · 9.1 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to 3.4.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 of `/v2` experimental interface 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 · moderate confidence

This is an Incorrect Authorization (broken access control) vulnerability in the experimental `/v2` API interface of Apache DolphinScheduler. The vulnerability allows unauthorized users to access or manipulate resources through the `/v2` endpoints due to improper authorization checks in the experimental interface.

MitigationUpgrade Apache DolphinScheduler to version 3.4.2 or later, which contains the fix for this authorization bypass 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 DolphinScheduler version
    Check the installed Apache DolphinScheduler version by inspecting the about page, startup logs, or the version file in the installation directory (common locations: UI footer, {install_dir}/LICENSE, or pom.xml if source deployment). Compare against the affected range: any version below 3.4.2.
    Affected if Installed version is below 3.4.2
  2. Verify /v2 API endpoint exposure
    Attempt to access the /v2 endpoint on your DolphinScheduler server (e.g., curl -k https://<host>:12345/dolphinscheduler/v2 or the respective API gateway path). Check if the endpoint responds (even with an error response) indicating it is exposed.
    Affected if The /v2 endpoint is reachable and responds to requests
  3. Check for authentication bypass
    Send a request to a protected resource via the /v2 API without valid credentials or with an invalid token. Observe if the API returns data or a 200-level response instead of rejecting the request with 401/403.
    Affected if Requests to /v2 API succeed without valid authentication or with invalid credentials
  4. Review API gateway or proxy configuration
    Inspect the DolphinScheduler configuration files (commonly in conf/ or config/ directory) or API gateway settings to determine if the experimental /v2 interface is explicitly enabled or routed.
    Affected if Configuration shows /v2 endpoint is enabled and publicly accessible

You are affected if your DolphinScheduler version is below 3.4.2 AND the experimental /v2 API interface is exposed and accessible, allowing unauthorized access to protected resources.

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 Apache DolphinScheduler to version 3.4.2 or later, which contains the fix for this authorization bypass vulnerability.

Recommended fix High confidence

3.4.2

  1. Ensure you have a complete backup of your DolphinScheduler database and configuration files
  2. Stop all running DolphinScheduler services
  3. Download Apache DolphinScheduler version 3.4.2 from the official Apache repository
  4. Follow the official upgrade documentation for your deployment method (kubernetes, docker, or standalone)
  5. Run database migrations if required by reviewing the release notes
  6. Start the upgraded DolphinScheduler services
  7. Verify the /v2 experimental interface is now properly protected and authorization is enforced
  8. Test that legitimate users have appropriate access to API endpoints
Caveat Review 3.4.2 release notes for any breaking changes in the v2 API or configuration changes

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

Fix this in Dolphinscheduler Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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