Apache SeaTunnel Web · UNSUPPORTED WHEN ASSIGNED Improper Authentication
Source GCVE Database
Not known to be exploited · end of life, no fix coming : replace or isolate Apache SeaTunnel Web; no fix will be released.
Data as of 18 Nov 2026, 10:51 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- None coming – the product is end of life
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
No fix will be released: Apache SeaTunnel Web is end of life. Replace it, or isolate it from untrusted networks until you can.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache SeaTunnel Weborg.apache.seatunnel:seatunnel-web | Affected
| Fixed in– |
Mavenorg.apache.seatunnel/seatunnel-webpkg:maven/org.apache.seatunnel/seatunnel-webOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vendor advises discontinuing use of Apache SeaTunnel Web 1.0.2. Users should migrate to supported alternatives or versions that include the account-status check implemented in later, unmaintained branches.
Description
Apache SeaTunnel Web 1.0.2 contains an improper authentication vulnerability that allows users with disabled accounts to authenticate successfully and obtain new login tokens. The login process does not verify account status, enabling continued access despite account disabling. This issue requires valid credentials and does not allow credential-free bypass. The product is no longer maintained, and no fixed release exists. Users are advised to discontinue use of this unsupported component.