CVE-2025-27531: Apache InLong · Deserialization of Untrusted Data
Affects Apache InLongSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.1.0 as a priority.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.1.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade org.apache.inlong/inlong to 2.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavenorg.apache.inlong/inlongpkg:maven/org.apache.inlong/inlongOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate this vulnerability effectively, European organizations should: 1) Immediately upgrade Apache InLong to version 2.1.0 or later, as this version contains the official patch addressing the deserialization flaw. 2) Implement strict input validation and sanitization on all serialized data inputs to prevent malicious payloads from being processed. 3) Restrict network access to Apache InLong management interfaces and APIs to trusted internal networks or VPNs, minimizing exposure to external threats. 4) Employ application-layer firewalls or intrusion detection/prevention systems (IDS/IPS) to monitor and block suspicious deserialization attempts or anomalous parameter manipulations. 5) Conduct thorough audits and monitoring of logs related to Apache InLong to detect any unusual file access patterns or parameter anomalies. 6) Establish a rapid incident response plan to isolate and remediate affected systems if exploitation is suspected. 7) Educate development and operations teams about secure deserialization practices and the risks associated with untrusted data processing.
Description
Deserialization of Untrusted Data vulnerability in Apache InLong. This issue affects Apache InLong: from 1.13.0 before 2.1.0, this issue would allow an authenticated attacker to read arbitrary files by double writing the param. Users are recommended to upgrade to version 2.1.0, which fixes the issue.