- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Do first: Apply the patch listed under Evidence.
Summary
Apache SeaTunnel Web is affected, and a user whose account has been disabled can log in with valid credentials and get a new login token that still works on protected APIs. The attacker must already have valid credentials for the disabled account, since this is not a credential-free bypass.
Original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach10/20Affects Maven packages
- Severity1/10Rated low by apache
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-128981 (Apache SeaTunnel Web: Disabled accounts can obtain new login tokens), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-128981 (entry last updated 2026-11-18):
Affected:
- Maven package org.apache.seatunnel:seatunnel-web: versions 1.0.2
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-128981 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128981 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Maven): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread.html/p4r5hhzxzsoxx12bk588w8rvsb39n8om
- https://github.com/apache/seatunnel-web/pull/264
- http://www.openwall.com/lists/oss-security/2026/11/18/3
- http://www.openwall.com/lists/oss-security/2026/11/18/4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-128981
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128981"}.Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
1.0.2
No fix released. The latest release, 1.0.2, is still affected.
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | lists.apache.org · thread.html/p4r5hhzxzsoxx12bk588w8rvsb39n8om |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-128981 |
| Record | NVD · CVE-2026-128981 |
| Write-ups 2Establishes: Technical detail and context. | |
| Link | openwall.com · lists/oss-security/2026/11/18/3 |
| Link | openwall.com · lists/oss-security/2026/11/18/4 |
| Other links 1 | |
| Patch | GitHub · apache/seatunnel-web · Pull request #264 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-128981
Is CVE-2026-128981 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-128981?
org.apache.seatunnel:seatunnel-web (Maven): version 1.0.2.Source: cve.now feed data