# CVE-2024-26579: Apache Inlong JDBC Vulnerability


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 8 May 2024
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-fgh3-pwmp-3qw3

## What is CVE-2024-26579?

CVE-2024-26579 is a critical vulnerability in Apache InLong, published on 8 May 2024. 

### Official description

Deserialization of Untrusted Data vulnerability in Apache InLong.This issue affects Apache InLong: from 1.7.0 through 1.11.0, 

 the attackers can bypass using malicious parameters.

Users are advised to upgrade to Apache InLong's 1.12.0 or cherry-pick [1], [2] to solve it.

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

[2]  https://github.com/apache/inlong/pull/9707

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-26579?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.inlong:manager-pojo` | Maven | From 1.7.0 | 1.12.0 |
| `org.apache.inlong:manager-pojo` | Maven | From 1.7.0 | 1.12.0 |

Products: Apache Inlong.

## How do I fix CVE-2024-26579?

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

## Is CVE-2024-26579 being exploited?

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

## Other vulnerabilities in Apache InLong

- [CVE-2026-63037](https://insights.sbomify.com/CVE-2026-63037/): Apache InLong: Unauthenticated SQL injection in Manager OpenAPI audit alert rule list endpoint (critical 9.8)
- [CVE-2026-63038](https://insights.sbomify.com/CVE-2026-63038/): Apache InLong: SQL Injection via String Concatenation Vulnerability Report (critical 9.8)
- [CVE-2026-63039](https://insights.sbomify.com/CVE-2026-63039/): Apache InLong: SQL Injection via Unvalidated MyBatis Dollar-Sign Interpolation in AuditAlertRuleService (critical 9.8)
- [CVE-2025-27531](https://insights.sbomify.com/CVE-2025-27531/): Apache InLong: An arbitrary file read vulnerability for JDBC (critical 9.8)
- [CVE-2023-51784](https://insights.sbomify.com/CVE-2023-51784/): Apache InLong: Remote Code Execution vulnerability in Apache InLong Manager (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-26579 and fix it if it is affected.

What it is: CVE-2024-26579 is a critical vulnerability in Apache InLong, published on 8 May 2024. 
Exploitation: There is no known exploitation of CVE-2024-26579 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.inlong:manager-pojo (Maven): affected from 1.7.0; fixed in 1.12.0
- org.apache.inlong:manager-pojo (Maven): affected from 1.7.0; fixed in 1.12.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-26579/ (Markdown: https://insights.sbomify.com/CVE-2024-26579/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-26579
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-26579
- OSV: https://osv.dev/vulnerability/CVE-2024-26579

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-26579/
Summaries are generated and may contain mistakes; the official description above is the record.