CVE-2026-128981: Apache SeaTunnel Web · Authentication bypass
Exploitation: None known · CVSS 9.8 Critical · Unauthenticated · Published 2026-11-18
Description
** UNSUPPORTED WHEN ASSIGNED ** Improper Authentication in Apache SeaTunnel Web 1.0.2 allows a user whose account has been disabled to authenticate with valid credentials and obtain a new login token. The login query does not check the account status, so disabling an account does not prevent new logins or access to protected APIs using the newly issued token. This issue requires valid credentials for the disabled account; it is not a credential-free authentication bypass. Apache SeaTunnel Web is no longer maintained. The affected 1.0.2 release does not contain the account-status check added to the main branch in pull request #264. There is no maintained fixed release. Users should discontinue use of this unsupported component. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
Enclave's analysis
Apache SeaTunnel Web's login code never checks whether an account has been disabled, so someone who still knows the password for a disabled account can log in and get a fresh working token. It only works if the attacker already holds valid credentials for that specific account — it is not an open-door bypass. No public exploit code or in-the-wild use has shown up, and Apache itself rates it low severity even though automated scoring calls it critical. There is no shipped fix; the only options are building from the unreleased main-branch patch or retiring the component.
Fix
No fixed version in the CVE record yet. Follow the vendor advisory.
Affected versions
| Product | Vulnerable | Fixed in |
|---|---|---|
| Apache SeaTunnel Web | 1.0.2 | Not listed |