CVE-2026-63038

Apache InLong: SQL Injection via String Concatenation Vulnerability Report

Published Aug 20, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
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 .

Analysis

AI-generated

Technical 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 the EPSS score is <1%, while its CVSS score of 9.8 denotes critical severity. 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.

Remediation

No solution or workaround provided in the CVE record.

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 24, 2026 at 19:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:apache:inlong:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
First Time appeared Apache
Apache inlong
Vendors & Products Apache
Apache inlong
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
Weaknesses
  • CWE-89

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

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Aug 24, 2026, 4:55 PM
Reserved
Jul 15, 2026, 3:40 AM
Status
Analyzed
Published
Aug 20, 2026, 4:17 PM
Modified
Oct 18, 2026, 8:10 PM