Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-29847: CWE-20 Improper Input Validation in Apache Software Foundation Apache Linkis

0
Unknown
VulnerabilityCVE-2025-29847cvecve-2025-29847cwe-20cwe-22
Published: Mon Jan 19 2026 (01/19/2026, 08:36:06 UTC)
Source: CVE Database V5
Vendor/Project: Apache Software Foundation
Product: Apache Linkis

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/list?dev@linkis.apache.org:2025-9:cve

AI-Powered Analysis

AILast updated: 01/19/2026, 09:11:35 UTC

Technical Analysis

CVE-2025-29847 is a security vulnerability identified in Apache Linkis, an open-source data integration and governance platform maintained by the Apache Software Foundation. The flaw exists in the handling of URL parameters within the JDBC engine and data source functionality. Specifically, when the URL parameter is subjected to multiple rounds of URL encoding, it can bypass the system's input validation checks. This improper input validation (CWE-20) combined with potential path traversal issues (CWE-22) allows an attacker to craft malicious JDBC parameters that may grant unauthorized access to system files. The vulnerability affects Apache Linkis versions from 1.3.0 up to and including 1.7.0. The root cause is that the system does not adequately decode URL-encoded characters before validating the input, allowing encoded payloads to evade detection. The recommended fix, implemented in version 1.8.0, involves continuously checking for the presence of the '%' character in connection information and performing URL decoding to ensure all encoded data is properly interpreted before validation. No public exploits have been reported, but the vulnerability could be leveraged in environments where Apache Linkis is exposed to untrusted users or inputs, potentially leading to unauthorized file access and information disclosure.

Potential Impact

For European organizations, the impact of this vulnerability can be significant, especially for those relying on Apache Linkis for data integration and governance in critical infrastructure, finance, healthcare, or government sectors. Unauthorized access to system files via JDBC parameters could lead to exposure of sensitive configuration files, credentials, or other protected data, undermining confidentiality and potentially integrity if attackers modify files. This could facilitate further lateral movement or privilege escalation within affected networks. The vulnerability does not appear to directly enable remote code execution or denial of service, but the unauthorized file access risk alone is concerning. Organizations with publicly accessible or poorly segmented Linkis deployments are at higher risk. Additionally, regulatory frameworks such as GDPR impose strict requirements on data protection; a breach resulting from this vulnerability could lead to compliance violations and financial penalties.

Mitigation Recommendations

European organizations should immediately upgrade Apache Linkis to version 1.8.0 or later, where the vulnerability is fixed. Until upgrade is possible, implement strict input validation and sanitization on all user-supplied JDBC parameters, ensuring multiple rounds of URL decoding are performed before validation. Restrict access to the Linkis frontend and JDBC engine interfaces to trusted networks and authenticated users only, minimizing exposure to untrusted inputs. Conduct thorough audits of existing JDBC connection configurations to detect any suspicious or malformed URL parameters. Employ network segmentation and monitoring to detect anomalous access patterns targeting Linkis services. Additionally, review and harden file system permissions to limit the impact of any unauthorized file access. Finally, maintain up-to-date backups and incident response plans to quickly recover from any exploitation attempts.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
apache
Date Reserved
2025-03-12T03:28:05.936Z
Cvss Version
null
State
PUBLISHED

Threat ID: 696df1ced302b072d99017b2

Added to database: 1/19/2026, 8:56:46 AM

Last enriched: 1/19/2026, 9:11:35 AM

Last updated: 1/19/2026, 10:11:34 AM

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats