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 .
Published: 2026-08-20
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Improper neutralization of special elements in SQL commands allows an attacker to inject malicious SQL statements through the dbName, tableName, schemaName, and username parameters. This flaw can result in the execution of unintended queries, leading to unauthorized data disclosure, modification, or deletion. The impact spans confidentiality, integrity, and availability of the underlying database.

Affected Systems

Apache InLong versions 2.0.0 up through 2.3.x are affected. The vendor is Apache Software Foundation and the product is Apache InLong. All installations using any of the vulnerable releases should be considered at risk.

Risk and Exploitability

The vulnerability is not listed in CISA KEV and no EPSS score is available, indicating no measured exploitation probability to date. Nevertheless, the ability to inject arbitrary SQL via exposed parameters suggests a high-risk scenario, especially if the service is reachable over the network. The attack vector is likely remote through any API or web interface that accepts the vulnerable parameters. The potential for data loss or tampering remains significant even without known exploitation reports.

Generated by OpenCVE AI on August 20, 2026 at 20:50 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Apache InLong to version 2.4.0 or newer.
  • If upgrading is not immediately possible, apply the cherry‑pick patch available at https://github.com/apache/inlong/issues/12135.
  • Re‑implement input handling for dbName, tableName, schemaName, and username to use parameterized queries or strict validation to prevent injection.
  • Monitor database logs for suspicious activity and consider deploying a database firewall to block anomalous queries.

Generated by OpenCVE AI on August 20, 2026 at 20:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 20 Aug 2026 18:30:00 +0000

Type Values Removed Values Added
First Time appeared Apache
Apache inlong
Vendors & Products Apache
Apache inlong

Thu, 20 Aug 2026 17:30:00 +0000

Type Values Removed Values Added
References

Thu, 20 Aug 2026 16:00:00 +0000

Type Values Removed Values Added
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 .
Title Apache InLong: SQL Injection via String Concatenation Vulnerability Report
Weaknesses CWE-89
References

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-08-20T17:09:17.259Z

Reserved: 2026-07-15T03:40:15.338Z

Link: CVE-2026-63038

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-20T16:17:29.760

Modified: 2026-08-20T17:19:14.390

Link: CVE-2026-63038

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-20T21:00:05Z

Weaknesses
  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')