Apache SeaTunnel SQL Injection vulnerabilityGHSA-8m84-h9hh-3cfh
HIGHGHSA-8m84-h9hh-3cfh is a high-severity (CVSS 7.5) CWE-552 vulnerability in org.apache.seatunnel:seatunnel. A fix is available for org.apache.seatunnel:seatunnel — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-8m84-h9hh-3cfh.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.seatunnel:seatunnelReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Mysql security vulnerability in Apache SeaTunnel.
Attackers can read files on the MySQL server by modifying the information in the MySQL URL
allowLoadLocalInfile=true&allowUrlInLocalInfile=true&allowLoadLocalInfileInPath=/&maxAllowedPacket=655360 This issue affects Apache SeaTunnel: 1.0.0.
Users are recommended to upgrade to version [1.0.1], which fixes the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.seatunnel:seatunnel | ≥ 1.0.0&&< 1.0.1 | 1.0.1org.apache.seatunnel:seatunnel:1.0.1 |
Affected Products
seatunnelapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.seatunnel:seatunnel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.seatunnel:seatunnel to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8m84-h9hh-3cfh is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-8m84-h9hh-3cfh in your dependencies?
Find it across Maven, including transitive dependencies.