CVE-2026-68573

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

GHSA-r2q4-f69c-qwfg ↗EUVD-2026-103148 ↗

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 Kylin >= 4.0.0, <= 5.0.4
CWE-287 Improper Authentication
ETK-2026-1940Zero's internal tracking ID, independent of the CVE number., permanent identifier
3d 06h 08msince last run
48mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+35h58m
0
+2h
+4h
+6h
+8h
+10h

description

Apache Kylin versions 4 through 5.0.4 do not properly restrict access to cleanup operations. An unauthenticated remote party may invoke those actions when a Kylin service is exposed to requests without an authentication boundary, particularly from public networks.

mitigation

Upgrade Apache Kylin to version 5.0.5. Until upgrading, restrict access to Kylin services to trusted networks and enforce authentication at the network boundary.

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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.25%14th percentile
agent run time
48m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 19:32Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-16 19:32Z
    ghsa: trigger signal, started the run
  2. 2026-10-16 19:32Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1940",
  "cve_id": "CVE-2026-68573",
  "display_id": "CVE-2026-68573",
  "ghsa_id": "GHSA-r2q4-f69c-qwfg",
  "euvd_id": "EUVD-2026-103148",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper authentication in Apache Kylin cleanup operations",
  "summary": "Apache Kylin versions 4 through 5.0.4 do not properly restrict access to cleanup operations. An unauthenticated remote party may invoke those actions when a Kylin service is exposed to requests without an authentication boundary, particularly from public networks.",
  "mitigation": "Upgrade Apache Kylin to version 5.0.5. Until upgrading, restrict access to Kylin services to trusted networks and enforce authentication at the network boundary.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Kylin",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.0.0, <= 5.0.4"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Apache Kylin",
      "purl": null
    }
  ],
  "cwes": [
    287
  ],
  "cvss_score": 9.8,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0025,
  "epss_percentile": 0.1498,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 48.23083335,
  "t0_at": "2026-10-16T19:32:22.205000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-16T19:32:22.205000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T19:32:22.205000+00:00",
      "url": "https://github.com/advisories/GHSA-r2q4-f69c-qwfg"
    }
  }
}

published 2026-10-18 06:41Z
last change 2026-10-21 12:26Z

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.