Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-9x53-gr7p-4qf5

Apache SeaTunnel: Unauthenticated insecure access

CVSS 6.5 MediumEPSS 0.012 · 67th percentile

Published by the GitHub Advisory Database at 19 Jun 2025, 12:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.seatunnel:seatunnel-engine-serverMaven<2.3.112.3.11
org.apache.seatunnel:seatunnel-engine-commonMaven<2.3.112.3.11
Identifiers
GHSA-9x53-gr7p-4qf5 · CVE-2025-32896
Weakness (CWE)
CWE-306
Tags
Published
19 Jun 2025
Updated
19 Jun 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache SeaTunnel's seatunnel-engine-server and seatunnel-engine-common Maven packages, versions before 2.3.11, let unauthenticated users submit jobs through the REST API, which can lead to arbitrary file read and deserialization attacks. An attacker needs only network access to the job submission endpoint, with no account required, and can abuse extra parameters in a MySQL URL to read files and trigger deserialization. Upgrade to version 2.3.11. The source also recommends enabling the REST API v2 and HTTPS two-way authentication.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N ADP (CISA-ADP)
  • CISA KEV Not listed.
  • EPSS 0.012, the 67th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:10 UTC First seen by agentprime
  2. 31 Oct 2026, 15:10 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.