# CVE-2026-63039: Apache InLong: SQL Injection via Unvalidated MyBatis Dollar-Sign Interpolation in AuditAlertRuleService

> Attackers can execute arbitrary SQL commands via unvalidated input in AuditAlertRuleService, potentially reading or modifying database contents.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-pg4r-4hvf-4rqh

## What is CVE-2026-63039?

CVE-2026-63039 is a critical SQL injection vulnerability in Apache InLong, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache InLong. This allows an attacker to inject the string value into
the SQL statement, enabling SQL injection.

This issue affects Apache InLong: from 2.0.0 before 2.4.0.

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

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

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-63039?

It affects 1 product.


Products: Apache Inlong.

## How do I fix CVE-2026-63039?

No fix has been published for CVE-2026-63039 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-63039 being exploited?

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

Public exploit code:

- Reproducer for CVE-2026-63039 (Apache InLong AuditAlertRule MyBatis ORDER BY SQL injection via orderField/orderType) (github_poc): https://github.com/oscerd/CVE-2026-63039

## 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-2025-27531](https://insights.sbomify.com/CVE-2025-27531/): Apache InLong: An arbitrary file read vulnerability for JDBC (critical 9.8)
- [CVE-2024-26579](https://insights.sbomify.com/CVE-2024-26579/): Apache Inlong JDBC Vulnerability (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-2026-63039 and fix it if it is affected.

What it is: CVE-2026-63039 is a critical SQL injection vulnerability in Apache InLong, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-63039 in the wild and no public exploit code.

Affected product: Apache InLong. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2026-63039/ (Markdown: https://insights.sbomify.com/CVE-2026-63039/index.md)
```

## Sources

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

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