CVE-2024-26580 Apache InLong: Logged-in user could exploit an arbitrary file read vulnerability

What is CVE-2024-26580?

CVE-2024-26580 is a critical unsafe deserialization vulnerability in Apache InLong, published on 6 Mar 2024. 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.8.0 through 1.10.0, the attackers can

use the specific payload to read from an arbitrary file. Users are advised to upgrade to Apache InLong's 1.11.0 or cherry-pick [1] to solve it.

[1] https://github.com/apache/inlong/pull/9673

Weakness: CWE-502

Which versions are affected by CVE-2024-26580?

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

Products include Apache Inlong.

How do I fix CVE-2024-26580?

Upgrade org.apache.inlong:manager-common to 1.11.0 or later.

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

Is CVE-2024-26580 being exploited?

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

Other vulnerabilities in Apache InLong

• CVE-2026-63037 Apache InLong: Unauthenticated SQL injection in Manager OpenAPI audit alert rule list endpoint Critical 9.8
• CVE-2026-63038 Apache InLong: SQL Injection via String Concatenation Vulnerability Report Critical 9.8
• CVE-2026-63039 Apache InLong: SQL Injection via Unvalidated MyBatis Dollar-Sign Interpolation in AuditAlertRuleService Critical 9.8
• CVE-2025-27531 Apache InLong: An arbitrary file read vulnerability for JDBC Critical 9.8
• CVE-2024-26579 Apache Inlong JDBC Vulnerability Critical 9.8

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as GHSA-p2gx-4434-pf6g.