CVE-2026-128981: Apache SeaTunnel Web: Disabled accounts can obtain new login tokens
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
Discontinue use of Apache SeaTunnel Web because it is unsupported.
Event History
Frequently Asked Questions
Who can exploit this issue?
An attacker needs valid credentials for an account that has been disabled. It is not exploitable as a credential-free authentication bypass.
Does disabling an account stop access?
No. In the affected release, the login process does not check account status, so a disabled account can obtain a new login token and use protected APIs.
Is a supported fixed version available?
No maintained fixed release is available because Apache SeaTunnel Web is no longer maintained. The recommended action is to discontinue use of this unsupported component.
How can I determine whether my deployment is affected?
Apache SeaTunnel Web 1.0.2 is affected because it lacks the account-status check. A practical validation is to test whether a disabled account with valid credentials can still log in and receive a new token.