Summary
Apache SeaTunnel: Unauthenticated insecure access
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.
Impact
A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.
Affected versions
Security releases
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.apache.seatunnel:seatunnel-engine-server to 2.3.11 or later; org.apache.seatunnel:seatunnel-engine-common to 2.3.11 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-32896? CVE-2025-32896 is a low-severity missing authentication for critical function vulnerability in org.apache.seatunnel:seatunnel-engine-server (maven), affecting versions < 2.3.11. It is fixed in 2.3.11. A critical operation is accessible without requiring any authentication.
- Which packages are affected by CVE-2025-32896?
org.apache.seatunnel:seatunnel-engine-server(maven) (versions < 2.3.11)org.apache.seatunnel:seatunnel-engine-common(maven) (versions < 2.3.11)
- Is there a fix for CVE-2025-32896? Yes. CVE-2025-32896 is fixed in 2.3.11. Upgrade to this version or later.
- Is CVE-2025-32896 exploitable, and should I be worried? Whether CVE-2025-32896 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-2025-32896 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-2025-32896?
- Upgrade
org.apache.seatunnel:seatunnel-engine-serverto 2.3.11 or later - Upgrade
org.apache.seatunnel:seatunnel-engine-commonto 2.3.11 or later
- Upgrade