CVE-2026-63038 Apache InLong: SQL Injection via String Concatenation Vulnerability Report

Critical 9.8 Published 20 Aug 2026 Updated 24 Aug 2026

Attackers can inject arbitrary SQL code via specific parameters in Apache InLong, potentially reading or modifying database contents.

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: None listed

What is CVE-2026-63038?

CVE-2026-63038 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 arbitrary SQL code through the dbName, tableName, schemaName, and username parameters.

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/issues/12135 .

Weakness: CWE-89

Which versions are affected by CVE-2026-63038?

It affects 1 product.

Products include Apache Inlong.

How do I fix CVE-2026-63038?

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

Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.

Is CVE-2026-63038 being exploited?

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

Sources

Also known as GHSA-8x82-h8qj-qg8w.