Overview
Apache InLong, a widely used data integration tool, has been found to possess a significant security vulnerability identified as CVE-2025-27528. This vulnerability stems from deserialization of untrusted data in Apache InLong which can potentially lead to system compromise or data leakage. The severity of the issue is further emphasized by its high CVSS score of 9.1. The vulnerability affects versions from 1.13.0 through 2.1.0 of Apache InLong and poses a serious threat to the integrity and security of systems utilizing these versions.
Vulnerability Summary
CVE ID: CVE-2025-27528
Severity: Critical (9.1 CVSS Score)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: System compromise or data leakage
Affected Products
Escape the Surveillance Era
Most apps won’t tell you the truth.
They’re part of the problem.
Phone numbers. Emails. Profiles. Logs.
It’s all fuel for surveillance.
Ameeba Chat gives you a way out.
- • No phone number
- • No email
- • No personal info
- • Anonymous aliases
- • End-to-end encrypted
Chat without a trace.
Product | Affected Versions
Apache InLong | 1.13.0 – 2.1.0
How the Exploit Works
The vulnerability arises from the deserialization of untrusted data in Apache InLong, specifically affecting the InLong JDBC. An attacker can exploit this by sending specially crafted data that, when deserialized, bypasses security mechanisms and enables arbitrary file reading. This could potentially allow an attacker to read sensitive data or execute malicious code leading to system compromise or data leakage.
Conceptual Example Code
Here is a conceptual example of a malicious payload that could be used to exploit this vulnerability:
POST /inlong/jdbc HTTP/1.1
Host: target.example.com
Content-Type: application/octet-stream
{ "serialized_object": "base64-encoded-serialized-object" }In the example above, the `serialized_object` field contains a base64-encoded serialized object that, when deserialized by the vulnerable Apache InLong JDBC, could lead to arbitrary file reading or execution of malicious code.
Mitigation
Users are strongly advised to upgrade to Apache InLong’s 2.2.0 or cherry-pick the fix from https://github.com/apache/inlong/pull/11747 to solve it. As a temporary mitigation, users can also apply a vendor patch or use Web Application Firewall (WAF) or Intrusion Detection Systems (IDS). However, these are not long-term solutions and upgrading to a fixed version is strongly recommended.