Authorization Flaw in org.apache.dolphinscheduler:dolphinscheduler-api (CVE-2026-42357)
Summary
Vulnerability in org.apache.dolphinscheduler:dolphinscheduler-api (CVE-2026-42357). Confidential information can be exposed externally. Mitigation: upgrade to 3.4.2 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42357 has been found in org.apache.dolphinscheduler:dolphinscheduler-api.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade org.apache.dolphinscheduler:dolphinscheduler-api to 3.4.2 or later.
If unsure, ask your IT team or search "org.apache.dolphinscheduler:dolphinscheduler-api CVE-2026-42357" on the vendor's site.
CVE-2026-42357 (org.apache.dolphinscheduler:dolphinscheduler-api) — CWE-863 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 3.4.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in org.apache.dolphinscheduler:dolphinscheduler-api.
Check the vendor advisory for the affected versions of org.apache.dolphinscheduler:dolphinscheduler-api.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 3.4.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.apache.dolphinscheduler:dolphinscheduler-api を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.apache.dolphinscheduler:dolphinscheduler-api to 3.4.2ステージング環境で 3.4.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web lists.apache.org
- web openwall.com
- web github.com