CVE-2025-27528 Apache InLong: JDBC Vulnerability for Invisible Character Bypass Leading to Arbitrary File Read

Critical 9.1 Published Updated

Attackers can bypass JDBC security mechanisms via deserialization to read arbitrary files in Apache InLong deployments.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2025-27528?

CVE-2025-27528 is a critical unsafe deserialization vulnerability in Apache InLong, published on 28 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

Deserialization of Untrusted Data vulnerability in Apache InLong.

This issue affects Apache InLong: from 1.13.0 through 2.1.0.

This vulnerability allows attackers to bypass the security mechanisms of InLong JDBC and leads to arbitrary file reading. 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

Weakness: CWE-502

Which versions are affected by CVE-2025-27528?

2 open source packages ship an affected version, including org.apache.inlong:manager-pojo. It affects 1 product.

PackageAffectedFixed in
org.apache.inlong:manager-pojo MavenFrom 1.13.02.2.0
org.apache.inlong:manager-pojo MavenFrom 1.13.02.2.0

Products include Apache Inlong.

How do I fix CVE-2025-27528?

Upgrade org.apache.inlong:manager-pojo to 2.2.0 or later.

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

Is CVE-2025-27528 being exploited?

There is no known exploitation of CVE-2025-27528 in the wild and no public exploit code.

Sources

Also known as GHSA-98v7-xxxv-hcrh.

Is CVE-2025-27528 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free