WhatBrokeToday
GTA 6FAQ
Apache

Apache SeaTunnel Web Improper Authentication Vulnerability (CVE-2026-128981)

critical

Is it fixed? Not yet.

Ongoing since Nov 18, 09:17 UTC. First reported Nov 18, 09:17 UTC.

What happened

An improper authentication vulnerability exists in Apache SeaTunnel Web 1.0.2, where disabled accounts can still authenticate using valid credentials and obtain a new login token. The login query fails to check the account status, allowing continued access to protected APIs. No official fix or workaround is provided in the report.

What caused it?

The login query does not check the account status, allowing a user whose account has been disabled to authenticate with valid credentials and obtain a new login token.

Source: tenable.com

No verified workaround yet

None of the linked reports describe a mitigation. This page updates when one appears.

Official fix

Timeline

  1. Investigating(current)
  2. Workaround available(upcoming)
  3. Resolved(upcoming)
  1. First report on security advisory

    Apache SeaTunnel Web: CVE-2026-128981 (Critical)

    Source

Evidence

1 report · 1 CVEShow
  1. [1]
    CVE First report
    Apache SeaTunnel Web: CVE-2026-128981 (Critical)(opens security advisory in a new tab)

    Critical severity. ** 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.…

    by Tenable 0upvotes 0comments

FAQ

What happened in the Apache issue?

An improper authentication vulnerability exists in Apache SeaTunnel Web 1.0.2, where disabled accounts can still authenticate using valid credentials and obtain a new login token. The login query fails to check the account status, allowing continued access to protected APIs. No official fix or workaround is provided in the report.

What is affected by the Apache issue?

Apache (versions: 1.0.2).

When did the Apache issue start and end?

It started Nov 18, 09:17 UTC and is still ongoing (19 h 26 min so far). This page updates as it develops.

How do I get alerts for Apache?

Subscribe to the Apache RSS feed for every new Apache incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Apache is down. Apache feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.