Skip to main content
VulnerabilityPublished Updated

CVE-2026-108762: Apache Kylin · Path-confinement Bypass During Metadata Backup Deletion

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-108762· High 7.3

Not known to be exploited · CVSS 7.3 High · fixed in 5.0.5 : patch Apache Kylin soon.

Data as of 30 Oct 2026, 21:07 UTC

CVSS 3.1 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.17.3
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.0.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Apache Software FoundationApache KylinAffected
  • >=4.0.0 <=5.0.4
Fixed in–
Mavenorg.apache.kylin/kylinpkg:maven/org.apache.kylin/kylinOther threatsAffected
  • >=4.0.0 <=5.0.4
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache Kylin to version 5.0.5 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated.

Description

A path-confinement bypass vulnerability exists in Apache Kylin versions 4.0.0 through 5.0.4 during metadata backup deletion. This flaw primarily impacts Kylin services exposed directly to public networks, which is uncommon. In-house deployments are generally not affected. The issue is resolved in version 5.0.5.

References

Community reviews

Loading reviews…