dbcve.org
LinkisApplication · Apache

CVE-2025-29847

HIGH · 7.5 CVSS v3.1 Published 2026-01-19
Fix available
A fix is available. Upgrade to 1.8.0 or later.
See remediation →
84/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
A vulnerability in Apache Linkis. Problem Description When using the JDBC engine and da When using the JDBC engine and data source functionality, if the URL parameter configured on the frontend has undergone multiple rounds of URL encoding, it may bypass the system's checks. This bypass can trigger a vulnerability that allows unauthorized access to system files via JDBC parameters. Scope of Impact This issue affects Apache Linkis: from 1.3.0 through 1.7.0. Severity level moderate Solution Continuously check if the connection information contains the "%" character; if it does, perform URL decoding. Users are recommended to upgrade to version 1.8.0, which fixes the issue. More questions about this vulnerability can be discussed here:  https://lists.apache.org/[email protected]:2025-9:cve

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 · moderate confidence

This is a URL encoding bypass vulnerability in Apache Linkis JDBC engine. When JDBC connection URLs undergo multiple rounds of URL encoding, the system's security checks can be bypassed, allowing unauthorized access to system files through specially crafted JDBC parameters.

MitigationUpgrade to Apache Linkis 1.8.0 and implement URL decoding checks for '%' characters in JDBC connection strings before validation.

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
LinkisApplication
Affected:>= 1.3.0, < 1.8.0

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
High
Integrity
None
Availability
None

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

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 Linkis installation version
    Locate the Linkis installation directory and check the version file or pom.xml. Common locations include /opt/linkis or the installation root. Look for a VERSION file or check the manifest/VERSION file within the Linkis home directory.
    Affected if The installed version is 1.3.0 or higher but lower than 1.8.0
  2. Confirm JDBC engine is deployed
    Check if the jdbc engineconn component is installed. Look for jdbc-related directories in the engines folder or check engine deployment configurations.
    Affected if The JDBC engine component is present and enabled in the Linkis deployment
  3. Identify JDBC connection URL processing
    Review Linkis configuration files (linkis-cg-jdbc.conf or similar) for JDBC datasource configurations. Check if user-provided JDBC URLs are accepted through APIs or job submission parameters.
    Affected if Users can submit JDBC connection URLs through Linkis job parameters or datasource configurations
  4. Check for URL validation on JDBC parameters
    Examine the JDBC datasource or engine connector code/configuration for validation logic that checks for encoded characters (especially '%') in connection URLs. Look for any security filter or validator implementations.
    Affected if No explicit validation exists for URL-encoded characters in JDBC connection strings, or the validation only performs single-pass decoding

A user is affected if their Apache Linkis version is between 1.3.0 and 1.7.x (inclusive), the JDBC engine is in use, and JDBC connection URLs are accepted without multi-stage URL decoding validation.

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 1.8.0 or later
Fixed in 1.8.0
Interim mitigation

Upgrade to Apache Linkis 1.8.0 and implement URL decoding checks for '%' characters in JDBC connection strings before validation.

Recommended fix High confidence

1.8.0

  1. Upgrade Apache Linkis from current version (1.3.0-1.7.0) to version 1.8.0 which contains the fix for this vulnerability.

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

Fix this in Linkis Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29847 — 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-29847 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