dbcve.org
DolphinschedulerApplication · Apache

CVE-2026-32966

CRITICAL · 9.8 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
DataSource API Missing Authorization Check Leads to Arbitrary Data Source Metadata Disclosure 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

Apache DolphinScheduler's DataSource API lacks proper authorization checks, allowing unauthenticated or unauthorized users to access arbitrary data source metadata. This critical vulnerability (CVSS 9.8) exposes sensitive connection information, credentials, and configuration details of configured data sources without authentication.

MitigationUpgrade Apache DolphinScheduler to version 3.4.2 or later. Until upgrade, restrict network access to the DolphinScheduler API endpoints and monitor for unauthorized metadata access attempts.

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
High

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

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 version by accessing the UI footer, checking docker image tags, or querying the /actuator/health or /version API endpoint if available
    Affected if Version is lower than 3.4.2 (e.g., 3.4.1, 3.4.0, 3.3.x, 3.2.x, or earlier)
  2. Verify API network exposure
    Determine if the DolphinScheduler API service (typically port 12345 or 8080) is exposed to untrusted networks or the public internet. Check firewall rules, load balancer configurations, or Kubernetes ingress settings.
    Affected if API endpoints are reachable from untrusted networks without authentication barriers
  3. Test DataSource API access without credentials
    Send an HTTP GET request to the data source API endpoint (e.g., /datasources or /resources/datasources) without providing any authentication tokens or credentials. Use a tool like curl: curl -s http://<host>:<port>/datasources
    Affected if The API returns data source metadata, connection strings, or credential information without requiring authentication

You are affected if running any Apache DolphinScheduler version below 3.4.2 AND the DataSource API is accessible without authentication, as indicated by the API returning sensitive data source information to unauthenticated requests.

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. Until upgrade, restrict network access to the DolphinScheduler API endpoints and monitor for unauthorized metadata access attempts.

Recommended fix High confidence

3.4.2

  1. Back up your current DolphinScheduler installation and database before proceeding
  2. Download Apache DolphinScheduler version 3.4.2 from the official Apache release repository
  3. Review and follow the official Apache DolphinScheduler upgrade guide for your deployment method
  4. Execute the upgrade process according to the upgrade documentation
  5. Verify the upgrade was successful and the authorization check is now enforced

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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