ETK-2026-338

validated

check availablenot proven exploitable

awaiting cvepublic pockev

Kiteworks system

ETK-2026-338, no cve assigned

−18dTTV

12mAI analysis

Check if you are vulnerable

timeline

0 = cve.org, not yet published

trigger signal −22dcheck available−18dagent stopped

−20d

−15d

−10d

−5d

description

Kiteworks reported fixing a security flaw affecting its Kiteworks system. The available evidence does not establish the affected function, attacker impact, or conditions required for exploitation.

mitigation

Apply current Kiteworks security updates and confirm the deployed system is on a vendor-supported release. Restrict externally reachable Kiteworks access to trusted users and networks until patch status is verified.

check

available

exploit

automation

contextual

auth required

–

EPSS

–

agent run time

12m

cve.org record, t = 0

not published yet

Δ to public poc

–

Δ to kev

–

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

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

2026-09-29 14:13Z
thehackernews: trigger signal, started the run
https://thehackernews.com/2026/09/kiteworks-fixes-critical-flaw-found.html

this entry in the feed

GET /api/v1/feed/ETK-2026-338

{
  "etk_id": "ETK-2026-338",
  "cve_id": null,
  "display_id": "ETK-2026-338",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Kiteworks system security flaw",
  "summary": "Kiteworks reported fixing a security flaw affecting its Kiteworks system. The available evidence does not establish the affected function, attacker impact, or conditions required for exploitation.",
  "mitigation": "Apply current Kiteworks security updates and confirm the deployed system is on a vendor-supported release. Restrict externally reachable Kiteworks access to trusted users and networks until patch status is verified.",
  "vendor": "Kiteworks",
  "product": "Kiteworks system",
  "affected": [],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 11.796810733333333,
  "t0_at": null,
  "signals": {
    "check": {
      "at": "2026-10-03T14:11:04.749480+00:00",
      "days": -17.610937451921295,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T04:50:49.767396+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-09-29T14:13:20+00:00",
      "days": -21.60937205238426,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T04:50:49.767396+00:00",
      "url": "https://thehackernews.com/2026/09/kiteworks-fixes-critical-flaw-found.html"
    }
  }
}

published 2026-10-02 13:27Z
last change 2026-10-21 04:28Z

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.