CVE-2025-29847
Apache Linkis: Arbitrary File Read via Double URL Encoding Bypass
Description
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
INFO
Published Date :
Jan. 19, 2026, 9:16 a.m.
Last Modified :
Jan. 19, 2026, 10:16 a.m.
Remotely Exploit :
No
Source :
[email protected]
Affected Products
The following products are affected by CVE-2025-29847
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Upgrade Apache Linkis to version 1.8.0 or later.
- Ensure JDBC connection URLs do not contain '%' characters.
- Decode URL parameters to prevent bypasses.
- Continuously check connection info for '%' and decode.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2025-29847.
| URL | Resource |
|---|---|
| https://lists.apache.org/thread/03l5rfkgdt022o75jp8x4tzpqxz8g057 | |
| http://www.openwall.com/lists/oss-security/2025/09/19/2 |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2025-29847 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2025-29847
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-29847 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2025-29847 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Jan. 19, 2026
Action Type Old Value New Value Added Reference http://www.openwall.com/lists/oss-security/2025/09/19/2 -
New CVE Received by [email protected]
Jan. 19, 2026
Action Type Old Value New Value Added Description 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 Added CWE CWE-22 Added CWE CWE-20 Added Reference https://lists.apache.org/thread/03l5rfkgdt022o75jp8x4tzpqxz8g057