Skip to content

Apache Kylin

Bug bounty on Sorona apache.org

Accepting reports open-source
Top reward
$1,500
Top severity paid
Critical
Assets in scope
12
Public CVEs
60
Last change
No changes yet

At a glance

What to know before you start testing.

Pays from $1,500
for critical bugs.
Partial safe harbor
Some legal protection; read the terms.
Publish after a fix
Coordinate the timing with the company.

Rewards

What Sorona lists as the payout for each severity.

Severity Reward
Critical $1,500+
High $700+
Medium $300+
Low $100 $100 / 1 month Claude Max
Safe harbor
Partial Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf.

Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

12 assets you may test, 6 excluded.

Web 1

  • https://kylin.apache.org

Products and areas 11

  • Kylin publishes no project-specific security policy. The declared path is the ASF-wide one, with Kylin listed in the foundation's project directory against [email protected], and no scope boundary is stated anywhere, so the whole Kylin tree is in
  • The build engine and the job scheduler, covering job submission, job configuration and what a job is permitted to do on the underlying cluster
  • The datasource connections to Hive, JDBC sources and streaming inputs, along with the credentials configured for each
  • The diagnostic package and log collection endpoints, and what they include about the cluster
  • The JDBC driver and any other client the project ships
  • The metadata store and every operation that reads or writes it, including how metadata written by one project is isolated from another
  • The model and cube definition path, where a definition submitted over the API becomes a build job on the cluster
  • The query pushdown path, where a query Kylin cannot answer from a cube is forwarded to an underlying engine
  • The query server and its entire REST API, including the administrative, system and diagnostic routes as well as the query endpoints
  • The web console and everything reachable from it, including its authentication and session handling
  • Users, roles and project-level access control, including how a permission decision is made and cached
Out of scope (6)
  • A deployment deliberately published to an untrusted network with default credentials in place, which is a deployment decision
  • Anything already covered by one of the six CVEs published in the past year
  • Findings against releases the project no longer ships
  • Hadoop, Hive, Spark, HBase and the other cluster components Kylin runs on, where Kylin is only the client
  • Resource exhaustion from a cube build the operator sized the cluster for
  • Upstream dependency vulnerabilities, unless Kylin's own use of the dependency makes them reachable

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Sorona's policy.

While testing

  • Report privately to the address on the policy page , Kylin's listed contact in the ASF project directory, naming Kylin clearly in the subject
  • Do not open a public GitHub issue or pull request describing the vulnerability before the fixed release ships
  • Check the recent CVEs before reporting.
  • Name the release you tested.
  • Include the HTTP request or the cube or model definition that triggers it, and state what credentials the request carried

Not accepted

  • Upstream dependency vulnerabilities, unless Kylin's own use of the dependency makes them reachable
  • Findings against releases the project no longer ships
  • Anything already covered by one of the six CVEs published in the past year
  • Resource exhaustion from a cube build the operator sized the cluster for
  • A deployment deliberately published to an untrusted network with default credentials in place

Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 1 hour ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD
CVESeverityPublished
CVE-2026-97355 Medium 6.5 5 Nov 2026
CVE-2026-97356 Medium 6.5 5 Nov 2026
CVE-2026-82960 High 8.8 5 Nov 2026
CVE-2026-83538 Medium 5.3 5 Nov 2026
CVE-2026-83542 Critical 9.8 5 Nov 2026
CVE-2026-84183 High 8.8 5 Nov 2026
CVE-2026-84728 Medium 5.4 5 Nov 2026
CVE-2026-85627 High 8.8 5 Nov 2026
CVE-2026-92887 High 7.3 5 Nov 2026
CVE-2026-82904 High 7.5 5 Nov 2026
CVE-2026-82907 Critical 9.8 5 Nov 2026
CVE-2026-82910 High 8.8 5 Nov 2026
CVE-2026-82912 High 8.8 5 Nov 2026
CVE-2026-82916 High 7.1 5 Nov 2026
CVE-2026-82902 Medium 4.3 5 Nov 2026
CVE-2026-114233 High 8.1 5 Nov 2026
CVE-2026-114235 Medium 6.5 5 Nov 2026
CVE-2026-114271 Medium 6.5 5 Nov 2026
CVE-2026-114272 Medium 6.5 5 Nov 2026
CVE-2026-114277 Medium 6.5 5 Nov 2026
CVE-2026-109129 Medium 5.4 5 Nov 2026
CVE-2026-109837 Medium 5.4 5 Nov 2026
CVE-2026-109856 Medium 6.5 5 Nov 2026
CVE-2026-109928 High 7.4 5 Nov 2026
CVE-2026-114229 Medium 6.1 5 Nov 2026
CVE-2026-59267 Medium 5.8 4 Nov 2026
CVE-2026-90631 Low 3.3 4 Nov 2026
CVE-2026-90632 Medium 5.5 4 Nov 2026
CVE-2026-90634 High 7.3 4 Nov 2026
CVE-2026-90624 High 7.3 4 Nov 2026
CVE-2026-90626 High 7.3 4 Nov 2026
CVE-2026-90627 Medium 5.5 4 Nov 2026
CVE-2026-90628 High 7.3 4 Nov 2026
CVE-2026-90629 High 7.3 4 Nov 2026
CVE-2026-59264 High 7.8 4 Nov 2026
CVE-2026-59268 High 7.3 4 Nov 2026
CVE-2026-59263 Low 1.9 4 Nov 2026
CVE-2026-64618 Critical 9.8 30 Oct 2026
CVE-2026-65874 High 8.8 30 Oct 2026
CVE-2026-95628 Medium 5.4 26 Oct 2026
CVE-2026-95629 Medium 5.4 26 Oct 2026
CVE-2026-95663 Medium 4.8 26 Oct 2026
CVE-2026-95664 Medium 5.4 26 Oct 2026
CVE-2026-101259 Medium 5.3 26 Oct 2026
CVE-2026-111497 Critical 9.2 22 Oct 2026
CVE-2026-88900 High 8.8 19 Oct 2026
CVE-2026-85313 Medium 4.3 19 Oct 2026
CVE-2026-85314 Medium 6.5 19 Oct 2026
CVE-2026-85315 Medium 5.3 19 Oct 2026
CVE-2026-85316 Medium 4.8 19 Oct 2026
CVE-2026-85317 Medium 4.8 19 Oct 2026
CVE-2026-85254 Medium 6.5 19 Oct 2026
CVE-2026-85257 Medium 5.3 19 Oct 2026
CVE-2026-85260 Medium 5.5 19 Oct 2026
CVE-2026-85296 Medium 6.5 19 Oct 2026
CVE-2026-85312 Medium 4.8 19 Oct 2026
CVE-2026-85247 Medium 5.9 19 Oct 2026
CVE-2026-85249 Medium 6.5 19 Oct 2026
CVE-2026-85250 High 7.5 19 Oct 2026
CVE-2026-85251 High 7.5 19 Oct 2026

Original policy

Copied from sorona.xyz on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Skip to content What this pays This project runs no bounty of its own. sorona.xyz pays you directly on qualified, reproduced findings. Severity │ sorona.xyz pays Critical │ $1,500+ High │ $700+ Medium │ $300+ Low │ $100 / 1 month Claude Max Submit a vulnerability CVE history 6 Last 12 months Auth/access control 35 % Remote code execution 30 % Info disclosure 20 % Input validation 15 % Latest advisories Loading the feed Overview Apache Kylin is an OLAP cube engine that pre-computes aggregates over Hadoop data so BI tools get sub-second answers, and it retains a real installed base in Chinese enterprise reporting. Development has slowed, though the project is live and outside the Attic. What stands out is the CVE density: six landed in the past year, two of them critical, against a project of modest size. Researchers are clearly working this target and none of them was paid for it. The Apache Software Foundation states that as a volunteer organisation it runs no bug bounty, and Kylin appears on no bounty platform. sorona.xyz pays you directly on qualified, reproduced findings. In scope Kylin publishes no project-specific security policy. The declared path is the ASF-wide one, with Kylin listed in the foundation's project directory against [email protected] , and no scope boundary is stated anywhere, so the whole Kylin tree is in The query server and its entire REST API, including the administrative, system and diagnostic routes as well as the query endpoints The web console and everything reachable from it, including its authentication and session handling The model and cube definition path, where a definition submitted over the API becomes a build job on the cluster The build engine and the job scheduler, covering job submission, job configuration and what a job is permitted to do on the underlying cluster The metadata store and every operation that reads or writes it, including how metadata written by one project is isolated from another Users, roles and project-level access control, including how a permission decision is made and cached The datasource connections to Hive, JDBC sources and streaming inputs, along with the credentials configured for each The query pushdown path, where a query Kylin cannot answer from a cube is forwarded to an underlying engine The JDBC driver and any other client the project ships The diagnostic package and log collection endpoints, and what they include about the cluster Out of scope Hadoop, Hive, Spark, HBase and the other cluster components Kylin runs on, where Kylin is only the client A deployment deliberately published to an untrusted network with default credentials in place, which is a deployment decision Upstream dependency vulnerabilities, unless Kylin's own use of the dependency makes them reachable Findings against releases the project no longer ships Anything already covered by one of the six CVEs published in the past year Resource exhaustion from a cube build the operator sized the cluster for Most-valued findings Anything reachable on the REST API without valid credentials, or with credentials that should not reach that route. The two criticals in the window, CVE-2026-62390 and CVE-2026-62392, mark the top of the published record Parameters that reach a shell, a job specification or a cluster command. A cube build is a Hadoop job assembled from a definition a user supplied, and that assembly step is the highest-value seam in the codebase The class the three highs of the window landed in, CVE-2025-61733, CVE-2025-61734 and CVE-2025-61735, which mark where the current wave of research is already productive Recovery of the credentials held for datasources and for the underlying cluster from configuration, from the metadata store or from a diagnostic package Project-level access control bypass, where a user of one project reads cubes or query results belonging to another Deserialisation of metadata or job state into object construction, a recurring shape in JVM data platforms of this generation Server-side request forgery from any endpoint that takes a datasource URL or fetches on the caller's behalf Program rules Submit through sorona.xyz. This project runs no bounty of its own; we validate, coordinate disclosure with the maintainers, and pay you directly. Report privately to [email protected] , Kylin's listed contact in the ASF project directory, naming Kylin clearly in the subject There is no money at any severity. The ASF runs no bug bounty as a foundation-wide position and no vendor pays for Kylin findings either Do not open a public GitHub issue or pull request describing the vulnerability before the fixed release ships Check the recent CVEs before reporting. Six landed in the past year and the surface is being actively worked, so duplication is a real risk here in a way it is not on quieter targets Name the release you tested. Development is slower than it once was, and a finding only counts if it reproduces against a version the project still ships Include the HTTP request or the cube or model definition that triggers it, and state what credentials the request carried Disclosure Handled under the ASF process: a private report to the security team, an embargoed fix agreed with the maintainers, then a public advisory and a CVE alongside the release carrying the fix. Kylin publishes through the ASF and NVD rather than as GitHub advisories. Release cadence is modest, so expect the embargo to run longer than on a fast-moving project, and hold the detail until the announcement. Safe harbor Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf. You are responsible for understanding and following the laws that apply to you, wherever you are, and for staying within any scope the project has defined. Submit a vulnerability