CVE-2025-27531 Apache InLong: An arbitrary file read vulnerability for JDBC
Critical 9.8
Published
Updated
Check this codebase for CVE-2025-27531 and fix it if it is affected.
What it is: CVE-2025-27531 is a critical vulnerability in Apache InLong, published on 6 Jun 2025.
Exploitation: There is no known exploitation of CVE-2025-27531 in the wild and no public exploit code.
Affected packages and fixed versions:
- org.apache.inlong:inlong-manager (Maven): affected from 1.13.0; fixed in 2.1.0
- org.apache.inlong:inlong-manager (Maven): affected from 1.13.0; fixed in 2.1.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-2025-27531/ (Markdown: https://insights.sbomify.com/CVE-2025-27531/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2025-27531?
CVE-2025-27531 is a critical vulnerability in Apache InLong, published on 6 Jun 2025.
Official description
Deserialization of Untrusted Data vulnerability in Apache InLong.
This issue affects Apache InLong: from 1.13.0 before 2.1.0,
this issue would allow an authenticated attacker to read arbitrary files by double writing the param.
Users are recommended to upgrade to version 2.1.0, which fixes the issue.
Weakness: CWE-502
Which versions are affected by CVE-2025-27531?
2 open source packages ship an affected version, including org.apache.inlong:inlong-manager. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.apache.inlong:inlong-manager Maven | From 1.13.0 | 2.1.0 |
org.apache.inlong:inlong-manager Maven | From 1.13.0 | 2.1.0 |
Products include Apache Inlong.
How do I fix CVE-2025-27531?
Upgrade org.apache.inlong:inlong-manager to 2.1.0 or later.
Is CVE-2025-27531 being exploited?
There is no known exploitation of CVE-2025-27531 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
- CVE-2026-63038 Apache InLong: SQL Injection via String Concatenation Vulnerability Report
- CVE-2026-63039 Apache InLong: SQL Injection via Unvalidated MyBatis Dollar-Sign Interpolation in AuditAlertRuleService
- CVE-2024-26579 Apache Inlong JDBC Vulnerability
- CVE-2023-51784 Apache InLong: Remote Code Execution vulnerability in Apache InLong Manager
Sources
Also known as GHSA-62gc-8jr5-x9pm.