CVE-2026-128981 json
Apache SeaTunnel Web: Disabled accounts can obtain new login tokens
published 2h ago modified 56m ago also EUVD-2026-128489
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
** 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.
Patch / fix
- github.com/apache/seatunnel-web#264 pull request
Is CVE-2026-128981 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.seatunnel:seatunnel-web | 1.0.2 |
no fix listed |
Affected products
- Apache Software Foundation Apache SeaTunnel Web
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
Sources
- CVE List CVE-2026-128981
- NVD CVE-2026-128981
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.