# CVE-2025-32896: Apache SeaTunnel: Unauthenticated insecure access > Unauthenticated attackers can submit jobs via REST API to achieve arbitrary file read and remote code execution through deserialization. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** Yes - **Published:** 19 Jun 2025 - **Updated:** 20 Jun 2025 - **Also known as:** GHSA-9x53-gr7p-4qf5 ## What is CVE-2025-32896? CVE-2025-32896 is a medium-severity missing authorization vulnerability in Apache SeaTunnel, published on 19 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description # Summary Unauthorized users can perform Arbitrary File Read and Deserialization attack by submit job using restful api-v1. # Details Unauthorized users can access `/hazelcast/rest/maps/submit-job` to submit job. An attacker can set extra params in mysql url to perform Arbitrary File Read and Deserialization attack. This issue affects Apache SeaTunnel: <=2.3.10 # Fixed Users are recommended to upgrade to version 2.3.11, and enable restful api-v2 & open https two-way authentication , which fixes the issue. Weakness: CWE-306 (Missing Authentication for Critical Functionality) ## Which versions are affected by CVE-2025-32896? 4 open source packages ship an affected version, including org.apache.seatunnel:seatunnel-engine-common and org.apache.seatunnel:seatunnel-engine-server. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.seatunnel:seatunnel-engine-common` | Maven | All versions | 2.3.11 | | `org.apache.seatunnel:seatunnel-engine-common` | Maven | All versions | 2.3.11 | | `org.apache.seatunnel:seatunnel-engine-server` | Maven | All versions | 2.3.11 | | `org.apache.seatunnel:seatunnel-engine-server` | Maven | All versions | 2.3.11 | Products: Apache Seatunnel. ## How do I fix CVE-2025-32896? Upgrade org.apache.seatunnel:seatunnel-engine-common to 2.3.11 or later. ## Is CVE-2025-32896 being exploited? There is no known exploitation of CVE-2025-32896 in the wild and no public exploit code. ## Other vulnerabilities in Apache SeaTunnel - [CVE-2023-48396](https://insights.sbomify.com/CVE-2023-48396/): Apache SeaTunnel Web: Authentication bypass (critical 9.1) - [CVE-2023-49198](https://insights.sbomify.com/CVE-2023-49198/): Apache SeaTunnel Web: Arbitrary file read vulnerability (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-32896 and fix it if it is affected. What it is: CVE-2025-32896 is a medium-severity missing authorization vulnerability in Apache SeaTunnel, published on 19 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-32896 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.seatunnel:seatunnel-engine-common (Maven): affected all versions; fixed in 2.3.11 - org.apache.seatunnel:seatunnel-engine-common (Maven): affected all versions; fixed in 2.3.11 - org.apache.seatunnel:seatunnel-engine-server (Maven): affected all versions; fixed in 2.3.11 - org.apache.seatunnel:seatunnel-engine-server (Maven): affected all versions; fixed in 2.3.11 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-2025-32896/ (Markdown: https://insights.sbomify.com/CVE-2025-32896/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32896 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32896 - OSV: https://osv.dev/vulnerability/CVE-2025-32896 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-32896/ Summaries are generated and may contain mistakes; the official description above is the record.