WaratekVRT Sign in

CVE-2026-128981

SeverityNot scored
WeaknessImproper authentication (CWE-287)
Published18 Nov 2026

Tagged unsupported-when-assigned. The affected software was already out of support when the CVE was assigned.

Not yet in NVD's feed. The description, CVSS score and weakness below come from the organisation that issued the CVE. NVD hasn't analysed it yet, and its NVD page may not exist yet.

Published today. NVD often adds the list of affected products days or weeks after a CVE is published, and the other sources we check lag too. The scope and status here may change.

Description

  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.

Exploitation status

No public exploit

No exploit has been reported in the sources we check.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment no assessment published
  • Indexed PoC none indexed
  • EPSS not scored

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists: apache/seatunnel-web #264.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active unsupported-when-assigned
Decided by Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all
Finding This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.
Candidate fix https://github.com/apache/seatunnel-web/pull/264 : a pull request: the change under review

References

URLTags
https://github.com/apache/seatunnel-web/pull/264 pr
https://lists.apache.org/thread.html/p4r5hhzxzsoxx12bk588w8rvsb39n8om vendor-advisory

Timeline

Published2026-11-18By the CVE Program.
NVD record modified2026-11-18NVD's own last-modified date for this record.