# CVE-2026-71897: Apache DolphinScheduler: Allows unauthorized workflow operations through batch-copy and batch-move endpoints

> Authenticated users can copy or move workflows from unauthorized projects due to improper authorization checks in batch endpoints.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-j93x-5w9j-p4gc

## What is CVE-2026-71897?

CVE-2026-71897 is a medium-severity missing authorization vulnerability in Apache DolphinScheduler, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An improper authorization check in Apache DolphinScheduler allows an authenticated user to use the batch-copy and batch-move endpoints to operate on workflows in projects for which they lack the required permissions. This may allow the user to copy or move workflows from unauthorized projects.

This issue affects Apache DolphinScheduler: before 3.4.3.

Users are recommended to upgrade to version 3.4.3, which fixes the issue.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-71897?


## How do I fix CVE-2026-71897?

No fix has been published for CVE-2026-71897 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-71897 being exploited?

There is no known exploitation of CVE-2026-71897 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71897 and fix it if it is affected.

What it is: CVE-2026-71897 is a medium-severity missing authorization vulnerability in Apache DolphinScheduler, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71897 in the wild and no public exploit code.

Affected product: Apache DolphinScheduler. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-71897/ (Markdown: https://insights.sbomify.com/CVE-2026-71897/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71897
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71897
- OSV: https://osv.dev/vulnerability/CVE-2026-71897

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-71897/
Summaries are generated and may contain mistakes; the official description above is the record.