9.8
Critical
org.apache.dolphinscheduler:dolphinscheduler-api

CVE-2026-32966

CVE-2026-32966 is a critical-severity incorrect authorization vulnerability in org.apache.dolphinscheduler:dolphinscheduler-api (maven), affecting versions < 3.4.2. It is fixed in 3.4.2.

Key facts
CVSS score
9.8
Critical
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
org.apache.dolphinscheduler:dolphinscheduler-api
Fixed in
3.4.2
Disclosed
2026

Summary

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.

Impact

What is incorrect authorization?

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

Severity and exposure

CVE-2026-32966 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (3.4.2). Upgrading removes the vulnerable code path.

Affected versions

maven

  • org.apache.dolphinscheduler:dolphinscheduler-api (< 3.4.2)

Security releases

  • org.apache.dolphinscheduler:dolphinscheduler-api → 3.4.2 (maven)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-32966 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-32966 is reachable in your applications. Get a demo

Remediation advice

Upgrade org.apache.dolphinscheduler:dolphinscheduler-api to 3.4.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-32966

What is CVE-2026-32966?

CVE-2026-32966 is a critical-severity incorrect authorization vulnerability in org.apache.dolphinscheduler:dolphinscheduler-api (maven), affecting versions < 3.4.2. It is fixed in 3.4.2. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.

How severe is CVE-2026-32966?

CVE-2026-32966 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.apache.dolphinscheduler:dolphinscheduler-api are affected by CVE-2026-32966?

org.apache.dolphinscheduler:dolphinscheduler-api (maven) versions < 3.4.2 is affected.

Is there a fix for CVE-2026-32966?

Yes. CVE-2026-32966 is fixed in 3.4.2. Upgrade to this version or later.

Is CVE-2026-32966 exploitable, and should I be worried?

Whether CVE-2026-32966 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-32966 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-32966?

Upgrade org.apache.dolphinscheduler:dolphinscheduler-api to 3.4.2 or later.

Stop the waste.
Protect your environment with Kodem.