Is CVE-2026-63038 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-63038 being exploited in the wild.

How severe is CVE-2026-63038?

Critical severity, with a CVSS score of 9.8, published 20 August 2026.

Which products and versions are affected?

Apache Inlong 2.0.0 to before 2.4.0.

Is there a fix for CVE-2026-63038?

A patch was published on 2026-08-20: Version 2.4.0 released with fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-63038 attacked?

It is attacked over the network.

Am I affected by CVE-2026-63038?

Check whether you run Apache Inlong at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-63038: Apache InLong SQL injection in database parameters

CVE-2026-63038 · Severity: critical · CVSS 9.8 · Published 2026-08-20

Apache InLong is a data integration platform used to collect and manage data flows across systems. An attacker can inject malicious SQL commands through database configuration parameters (database name, table name, schema name, and username), allowing unauthorized access to or manipulation of the underlying database and potentially leading to data theft or service disruption.

Technologies: Apache Inlong. Vendors: Apache.

Quick answers

Is CVE-2026-63038 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-63038 being exploited in the wild.
How severe is CVE-2026-63038?: Critical severity, with a CVSS score of 9.8, published 20 August 2026.
Which products and versions are affected?: Apache Inlong 2.0.0 to before 2.4.0.
Is there a fix for CVE-2026-63038?: A patch was published on 2026-08-20: Version 2.4.0 released with fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-63038 attacked?: It is attacked over the network.
Am I affected by CVE-2026-63038?: Check whether you run Apache Inlong at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

This is a SQL injection vulnerability caused by improper neutralization of special characters in user-supplied input used in SQL commands. The vulnerability exists in parameters such as dbName, tableName, schemaName, and username, which are concatenated directly into SQL queries without proper sanitization or parameterized query techniques. An attacker with network access to the affected InLong instance can craft malicious input containing SQL metacharacters to execute arbitrary SQL code with the privileges of the application's database account. The vulnerability affects Apache InLong versions 2.0.0 through 2.3.x; patch version 2.4.0 is available.

Affected products

Apache InLong 2.0.0 to before 2.4.0

Timeline

2026-08-20: disclosed
2026-08-20: patched: Version 2.4.0 released with fix

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.