Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.8
CVE-2026-128981: Apache SeaTunnel Web lets disabled users log in again
CVE-2026-128981 · published 4 days ago
Summary
In version 1.0.2 of Apache SeaTunnel Web, a user whose account has been disabled can still log in with the correct password and receive a new authentication token. Because the system does not check the account’s disabled status, the user can continue to access protected features. The software is no longer maintained, so the recommended action is to stop using this component and switch to a supported alternative.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Vendor | Product | Affected versions |
|---|---|---|
| apache software foundation | apache seatunnel web | 1.0.2 |
Original advisory text
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.
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.
References
- https://github.com/apache/seatunnel-web/pull/264 Patch
- https://lists.apache.org/thread.html/p4r5hhzxzsoxx12bk588w8rvsb39n8om Vendor Advisory
- http://www.openwall.com/lists/oss-security/2026/11/18/3 URL
- http://www.openwall.com/lists/oss-security/2026/11/18/4 URL
- https://repo.maven.apache.org/maven2 URL
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/128xxx/CVE-2026-1289... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-128981 Vendor Advisory
Internet-facing
3 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically
- Gives an attacker full control
Severity
9.8
Critical
Type
CWE-287Improper Authentication
Timeline
Published18 Nov 2026
Updated22 Nov 2026
First seen18 Nov 2026
Track software like this
Free during beta