CVE-2025-27526 Apache InLong: JDBC Vulnerability For URLEncode and backspace bypass

Medium 6.5 Published Updated

Attackers can exploit a deserialization flaw in Apache InLong to achieve remote code execution via JDBC bypass techniques.

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-27526?

CVE-2025-27526 is a medium-severity 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 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

Weakness: CWE-502

Which versions are affected by CVE-2025-27526?

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-27526?

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-27526 being exploited?

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

Sources

Also known as GHSA-532x-j9r7-8f73.

Is CVE-2025-27526 in your software?

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

Check your SBOMs for free