How do I check whether I am affected by CVE-2026-68572?

- Check the installed Apache Kylin version and see whether it falls in the range `4` through `5.0.4` - unknown

What is the fix for CVE-2026-68572?

- Upgrade Apache Kylin to `5.0.5`

Who is not affected by CVE-2026-68572?

Not affected if: version-outside-4-to-5.0.4.

Live › vulnerability › CVE-2026-68572

Go to dashboard

high7.5Package

Apache Kylin: sensitive information exposed to unauthorized actors in 4 through 5.0.4

Apache Kylin versions 4 through 5.0.4 expose sensitive information to actors who should not see it. The sources do not say which data leaks or what an attacker can do with it.

Summary written from the sources below. Check the originals before acting.

CVSS 3.x

7.5

high

scored by 134c704f-9b21-4f2e-91b3-4a467353bcc0

known so far3 of 6

missing: versions, primary source, exploitation

First public: Oct 16, 2026 UTC
Last modified: Oct 20, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.

Why it is high, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: Not known from the sources.
Needs a special setup: Not known from the sources.
Reachable from: Not known from the sources.
Worst case: Sensitive information readable by unauthorized actors; exact data unknown.
CVSS said: 7.5. The facts above say low; we keep the sources' high until an analyst looks.

Who is affected

Teams running Apache Kylin 4 through 5.0.4 are affected. The sources do not describe the data path or configuration that exposes the information, so teams on other versions can likely skip it.

Know the next one before it finds you.

Add to Slack

Live › vulnerability › CVE-2026-68572

Go to dashboard

high7.5Package

Apache Kylin: sensitive information exposed to unauthorized actors in 4 through 5.0.4

Apache Kylin versions 4 through 5.0.4 expose sensitive information to actors who should not see it. The sources do not say which data leaks or what an attacker can do with it.

Summary written from the sources below. Check the originals before acting.

CVSS 3.x

7.5

high

scored by 134c704f-9b21-4f2e-91b3-4a467353bcc0

known so far3 of 6

missing: versions, primary source, exploitation

First public: Oct 16, 2026 UTC
Last modified: Oct 20, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.

Why it is high, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: Not known from the sources.
Needs a special setup: Not known from the sources.
Reachable from: Not known from the sources.
Worst case: Sensitive information readable by unauthorized actors; exact data unknown.
CVSS said: 7.5. The facts above say low; we keep the sources' high until an analyst looks.

Who is affected

Teams running Apache Kylin 4 through 5.0.4 are affected. The sources do not describe the data path or configuration that exposes the information, so teams on other versions can likely skip it.

Know the next one before it finds you.

Add to Slack

Apache Kylin: sensitive information exposed to unauthorized actors in 4 through 5.0.4

Why it is high, and not just CVSS

Who is affected

Know the next one before it finds you.

Apache Kylin: sensitive information exposed to unauthorized actors in 4 through 5.0.4

Why it is high, and not just CVSS

Who is affected

Know the next one before it finds you.

How to check

The fix

Who had it, and when

What the sources say, verbatim

Sources