CVE-2026-69076

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

GHSA-8x2p-cwp9-gghm ↗EUVD-2026-103149 ↗

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-200 Exposure of Sensitive Information to an Unauthorized Actor
ETK-2026-2026Zero's internal tracking ID, independent of the CVE number., permanent identifier
22h 26msince last run
1h 36mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+83h45m
0
+2h
+4h
+6h
+8h
+10h

description

Apache Kylin versions 4 through 5.0.4 do not adequately restrict access to job-discard operations. An unauthenticated actor may discard jobs when a Kylin service is exposed to a reachable network, particularly the public internet.

mitigation

Upgrade Apache Kylin to version 5.0.5. Until upgraded, restrict network access to Kylin services so untrusted users cannot reach them.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.20%8th percentile
agent run time
1h 36m
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

Contextual: an exploit technique exists, 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.

  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-69076

{
  "etk_id": "ETK-2026-2026",
  "cve_id": "CVE-2026-69076",
  "display_id": "CVE-2026-69076",
  "ghsa_id": "GHSA-8x2p-cwp9-gghm",
  "euvd_id": "EUVD-2026-103149",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper authorization for job discard in Apache Kylin",
  "summary": "Apache Kylin versions 4 through 5.0.4 do not adequately restrict access to job-discard operations. An unauthenticated actor may discard jobs when a Kylin service is exposed to a reachable network, particularly the public internet.",
  "mitigation": "Upgrade Apache Kylin to version 5.0.5. Until upgraded, restrict network access to Kylin services so untrusted users cannot reach them.",
  "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": [
    200
  ],
  "cvss_score": 7.5,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": 0.002,
  "epss_percentile": 0.0891,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 95.98485693333333,
  "t0_at": "2026-10-16T19:32:39.538000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-16T19:32:39.538000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T19:32:39.538000+00:00",
      "url": "https://github.com/advisories/GHSA-8x2p-cwp9-gghm"
    }
  }
}

published 2026-10-19 01:28Z
last change 2026-10-21 05:31Z

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.