CVE-2025-29847
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2026-01-19

Last updated on: 2026-01-27

Assigner: Apache Software Foundation

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
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-19
Last Modified
2026-01-27
Generated
2026-06-16
AI Q&A
2026-01-19
EPSS Evaluated
2026-06-15
NVD
CVE-2025-29847
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
apache linkis From 1.3.0 (inc) to 1.8.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-20 The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability in Apache Linkis occurs when the JDBC engine and data source functionality use a URL parameter on the frontend that has been encoded multiple times. This multiple URL encoding can bypass the system's checks, allowing unauthorized access to system files through JDBC parameters.

Impact Analysis

The vulnerability can allow unauthorized users to access system files via JDBC parameters, potentially exposing sensitive data or system information, which could lead to further exploitation or compromise of the system.

Detection Guidance

Detection involves checking if the connection information used in the JDBC engine contains the '%' character, which indicates URL encoding that may bypass system checks. You can monitor or log JDBC connection URLs and inspect them for multiple rounds of URL encoding (presence of '%' characters). Specific commands are not provided in the available resources.

Mitigation Strategies

Immediate mitigation steps include continuously checking if the connection information contains the '%' character and performing URL decoding if it does. The recommended solution is to upgrade Apache Linkis to version 1.8.0, which fixes the issue.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-29847. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart