Skip to content
Heist/ feed
Back to feed
High

Apache Linkis: Arbitrary File Read via Double URL Encoding Bypass

Type: advisorySources: OSV

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

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2025-29847
Confirmed fixed CVEs
Not specified
Updated in this feed
2 Nov 2026, 16:49 UTC · Revision 1

Source evidence

Apache Linkis: Arbitrary File Read via Double URL Encoding Bypass

core-osv · Original source

Published 19 Jan 2026, 08:36 UTC

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

osv:CVE-2025-29847
Complete source record
{
  "id": "3d1a9aa8b392d57f461bb575cd737c14423733a416fd50900b6aab00017b8d88",
  "url": "https://osv.dev/vulnerability/CVE-2025-29847",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Apache Linkis: Arbitrary File Read via Double URL Encoding Bypass",
    "summary": "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",
    "evidence": "osv:CVE-2025-29847",
    "products": [],
    "severity": "high",
    "structured": {
      "id": "CVE-2025-29847",
      "aliases": [
        "CVE-2025-29847",
        "GHSA-c399-q49h-qwc8"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/apache/linkis",
              "type": "GIT",
              "events": [
                {
                  "introduced": "9826dd922e711fe307b91f1c22f399988289c3be"
                },
                {
                  "fixed": "049ad8ed51454e2f4e1cfff581aee8a10d6246f2"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "cpe": "cpe:2.3:a:apache:linkis:*:*:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "1.3.0"
                      },
                      {
                        "fixed": "1.8.0"
                      }
                    ],
                    "source": "CPE_RANGE"
                  }
                ]
              }
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-29847.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:21.091854169Z",
      "provider": "osv",
      "references": [
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/29xxx/CVE-2025-29847.json",
        "https://lists.apache.org/thread/03l5rfkgdt022o75jp8x4tzpqxz8g057",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-29847"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-20",
          "CWE-22"
        ],
        "cna_assigner": "apache",
        "unresolved_ranges": [
          {
            "extracted_events": [
              {
                "range": [
                  {
                    "introduced": "1.3.0"
                  },
                  {
                    "last_affected": "1.7.0"
                  }
                ],
                "source": "AFFECTED_FIELD",
                "strategy": "StandardRange"
              }
            ]
          }
        ],
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/29xxx/CVE-2025-29847.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-29847",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 487386,
  "published_at": "2026-01-19T08:36:06.839+00:00"
}