Skip to main content
CVE-2025-27526VulnerabilityPublished

CVE-2025-27526: Apache InLong · Deserialization of Untrusted Data

Affects Apache InLongSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium · fixed in 2.2.0 : update Apache InLong when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

Affected software

ProductAffectedFixed in
GitHubapache/inlongpkg:github/apache/inlongOther threatsAffected
  • =1.13.0
  • <=2.1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations using Apache InLong should immediately upgrade to version 2.2.0 or later, where this vulnerability is fixed. If upgrading is not immediately feasible, they should apply the specific patch referenced in the Apache InLong GitHub pull request #11747 to remediate the issue. It is also recommended to audit and monitor network traffic for unusual serialized data inputs and implement strict input validation and deserialization controls. Employing application-layer firewalls or runtime application self-protection (RASP) solutions can help detect and block malicious deserialization attempts. Additionally, organizations should review their data integration workflows to ensure that only trusted sources provide serialized data and consider isolating critical data processing components to limit the blast radius of any potential exploit. Regular security assessments and code reviews focusing on deserialization logic are advised to prevent similar vulnerabilities.

Description

Deserialization of Untrusted Data vulnerability in Apache InLong. This issue affects Apache InLong: from 1.13.0 through 2.1.0. This vulnerability which can lead to JDBC Vulnerability URLEncdoe and backspace bypass. Users are advised to upgrade to Apache InLong's 2.2.0 or cherry-pick [1] to solve it. [1]  https://github.com/apache/inlong/pull/11747

References

Community reviews

Loading reviews…