CVE-2026-128981

waiting for further signalsZero needs more public information before it can validate it.

GHSA-35fq-5c7c-4jhr ↗EUVD-2026-128489 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Apache Software Foundation Apache SeaTunnel Web 1.0.2
CWE-287 Improper Authentication
ETK-2026-4782Zero's internal tracking ID, independent of the CVE number., permanent identifier
11h 05msince last run
43mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h59m
0
+4h
+6h
+8h
+10h
+12h

description

Apache SeaTunnel Web 1.0.2 fails to enforce account deactivation during sign-in. Someone with valid credentials for a disabled account can obtain a new session token and access protected APIs; this requires possession of that account's credentials.

mitigation

Remove Apache SeaTunnel Web 1.0.2 from service and migrate to a supported alternative, as no maintained fixed release is identified. Until it is retired, restrict access and revoke credentials for disabled accounts.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
43m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-18 08:50Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-18 08:50Z
    ghsa: trigger signal, started the run
  2. 2026-11-18 08:50Z

this entry in the feed

GET /api/v1/feed/CVE-2026-128981

{
  "etk_id": "ETK-2026-4782",
  "cve_id": "CVE-2026-128981",
  "display_id": "CVE-2026-128981",
  "ghsa_id": "GHSA-35fq-5c7c-4jhr",
  "euvd_id": "EUVD-2026-128489",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Disabled-account authentication bypass in Apache SeaTunnel Web",
  "summary": "Apache SeaTunnel Web 1.0.2 fails to enforce account deactivation during sign-in. Someone with valid credentials for a disabled account can obtain a new session token and access protected APIs; this requires possession of that account's credentials.",
  "mitigation": "Remove Apache SeaTunnel Web 1.0.2 from service and migrate to a supported alternative, as no maintained fixed release is identified. Until it is retired, restrict access and revoke credentials for disabled accounts.",
  "vendor": "Apache Software Foundation",
  "product": "Apache SeaTunnel Web",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.0.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "org.apache.seatunnel:seatunnel-web",
      "purl": null
    }
  ],
  "cwes": [
    287
  ],
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 43.014129016666665,
  "t0_at": "2026-11-18T08:50:16.327000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-18T08:50:16.327000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T08:50:16.327000+00:00",
      "url": "https://github.com/advisories/GHSA-35fq-5c7c-4jhr"
    }
  }
}

published 2026-11-18 10:06Z
last change 2026-11-18 21:29Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.