Skip to main content
VulnerabilityPublished

CVE-2026-128981: Apache SeaTunnel Web · Improper Authentication

Affects Apache SeaTunnel WebSource CVE Database V5

0
Compare

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, 09:07 UTC

Severity
High

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

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Apache SeaTunnel Weborg.apache.seatunnel:seatunnel-webAffected
  • =1.0.2
Fixed in–
Mavenorg.apache.seatunnel/seatunnel-webpkg:maven/org.apache.seatunnel/seatunnel-webOther threatsAffected
  • =1.0.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should discontinue use of this unsupported component to mitigate the risk. No other vendor-provided mitigations are available.

Description

Apache SeaTunnel Web 1.0.2 contains an improper authentication vulnerability where disabled user accounts can still authenticate successfully using valid credentials. The login process does not verify account status, allowing disabled accounts to obtain new login tokens and access protected APIs. This issue requires valid credentials and does not allow credential-free bypass. The product is no longer maintained, and no fixed release is available.

References

Community reviews

Loading reviews…