dbcve.org
KylinApplication · Apache

CVE-2025-61735

HIGH · 7.3 CVSS v3.1 Published 2025-10-02
Fix available
A fix is available. Upgrade to 5.0.3 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Server-Side Request Forgery (SSRF) vulnerability in Apache Kylin. This issue affects Apache Kylin: from 4.0.0 through 5.0.2. You are fine as long as the Kylin's system and project admin access is well protected. Users are recommended to upgrade to version 5.0.3, which fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Kylin versions 4.0.0 through 5.0.2 contain a Server-Side Request Forgery (SSRF) vulnerability that allows attackers to induce the server to make arbitrary HTTP requests to internal or external resources. This could enable reconnaissance of internal network services, access to cloud metadata endpoints, or pivoting to internal systems.

MitigationUpgrade to Apache Kylin version 5.0.3. As a compensating control, ensure Kylin's system and project admin access is properly protected with strong authentication and network segmentation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
KylinApplication
Affected:>= 4.0.0, < 5.0.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Kylin installed version
    Locate the Kylin installation directory and check the version file or use the kylin version command if available. Common locations include /opt/kylin or the directory set during installation.
    Affected if The installed version is 4.0.0 through 5.0.2 (versions >= 4.0.0 and < 5.0.3)
  2. Verify Kylin web interface accessibility
    Attempt to access the Kylin web UI over the network on its default port (7070 for Kylin 4.x, 16500 for Kylin 5.x) from an untrusted network perspective.
    Affected if The web interface is exposed to untrusted networks without proper network segmentation
  3. Check authentication configuration
    Review the Kylin configuration files (kylin.properties or similar) for authentication settings and verify that admin/project admin accounts use strong passwords.
    Affected if Authentication is weak, default credentials are in use, or admin access is not properly secured
  4. Inspect network exposure
    Use netstat or similar tools to determine which network interfaces and ports Kylin is listening on, and verify that only trusted networks can reach the Kylin service.
    Affected if Kylin is listening on 0.0.0.0 or an interface exposed to untrusted networks

You are affected if Apache Kylin version 4.0.0 through 5.0.2 is installed AND the web interface or API endpoints are accessible to untrusted networks without proper authentication and network segmentation controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.0.3 or later
Fixed in 5.0.3
Interim mitigation

Upgrade to Apache Kylin version 5.0.3. As a compensating control, ensure Kylin's system and project admin access is properly protected with strong authentication and network segmentation.

Recommended fix High confidence

5.0.3

  1. 1. Backup your current Apache Kylin installation, configuration, and metadata
  2. 2. Download Apache Kylin version 5.0.3 from the official Apache Kylin download page or repository
  3. 3. Stop the running Kylin service
  4. 4. Upgrade Kylin to version 5.0.3 following the standard upgrade procedure for your deployment method
  5. 5. Verify the upgrade was successful by checking the Kylin version
  6. 6. Start the Kylin service
  7. 7. Validate that critical workflows and queries function correctly after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kylin Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61735 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-61735 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data