CVE-2026-128981

Apache SeaTunnel Web: Disabled accounts can obtain new login tokens

Published Nov 18, 2026 CVSS n/a EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability in Apache SeaTunnel Web 1.0.2 permits a disabled user account to be authenticated again by creating a new login token, bypassing the intended account-status check. The login endpoint fails to verify that the account is disabled, so valid credentials continue to work. This flaw allows an attacker who possesses the disabled account's credentials to perform authenticated requests against protected APIs, potentially accessing sensitive data or internal services. The weakness is an authentication bypass (CWE-287).

Affected Systems

Affected product is Apache SeaTunnel Web version 1.0.2 from the Apache Software Foundation. No other versions are noted, and the source indicates that this release is no longer maintained and contains no fixes for the account status check added in pull request #264. Because the component is unsupported, there is no official fixed release available.

Risk and Exploitability

The vulnerability requires valid credentials for the disabled account; it is not a credential-free bypass. The EPSS score is not available and the issue is not listed in the CISA KEV catalog, so the likelihood of exploitation cannot be quantified objectively. However, if an attacker obtains a victim's disabled account credentials through phishing, credential reuse, or a prior breach, they can bypass the account lockout and gain access to internal APIs. The exploitation path is straightforward: submit the blocked user's real username and password to the login endpoint, receive a new token, and use that token to make authorized requests. The overall risk depends largely on the strength of the disabled account passwords and the sensitivity of the protected API endpoints.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Discontinue use of Apache SeaTunnel Web 1.0.2 and any other unsupported components
  • Migrate users and services to a supported, actively maintained data integration platform or a newer version if available
  • If migration is not feasible, isolate the application behind strict firewall rules, monitor for login activity, and enforce rigorous credentials management

Generated by OpenCVE AI on November 19, 2026 at 04:19 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Apache Software Foundation
Apache Software Foundation apache Seatunnel Web
Vendors & Products Apache Software Foundation
Apache Software Foundation apache Seatunnel Web
Type Values Removed Values Added
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.
Title Apache SeaTunnel Web: Disabled accounts can obtain new login tokens
Weaknesses CWE-287
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Nov 18, 2026, 10:05 AM
Reserved
Nov 13, 2026, 1:50 PM
Status
Received
Published
Nov 18, 2026, 9:17 AM
Modified
Nov 18, 2026, 10:16 AM