CVE-2026-63037
Received Received - Intake

SQL Injection in Apache InLong

Publication date: 2026-08-20

Last updated on: 2026-08-20

Assigner: Apache Software Foundation

Description
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache InLong. This appears to allow SQL injection in the ORDER BY clause against the Manager backend database. 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/12079 .

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-20
Last Modified
2026-08-20
Generated
2026-08-20
AI Q&A
2026-08-20
EPSS Evaluated
N/A
NVD
CVE-2026-63037
EUVD
EUVD-2026-63398

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
apache inlong From 2.0.0 (inc) to 2.4.0 (exc)
apache inlong 2.4.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is an SQL injection vulnerability in Apache InLong versions 2.0.0 to 2.4.0. It allows attackers to inject malicious SQL commands into the ORDER BY clause of queries against the Manager backend database. This occurs due to improper neutralization of special elements in user input.

Detection Guidance

Detection requires checking Apache InLong versions. Run: curl -s http://<inlong-manager-host>:<port>/api/version | grep version. If version is between 2.0.0 and 2.3.9, the system is vulnerable.

Impact Analysis

An attacker could exploit this to read, modify, or delete sensitive data in the backend database. This may lead to unauthorized access, data breaches, or complete system compromise depending on database permissions. Users running affected versions are at risk.

Compliance Impact

This vulnerability could lead to violations of GDPR (data protection) and HIPAA (health data privacy) by enabling unauthorized access to personal or sensitive data. Organizations may face legal penalties, reputational damage, and compliance audit failures if exploited.

Mitigation Strategies

Upgrade Apache InLong to version 2.4.0 or later. Alternatively, apply the patch from https://github.com/apache/inlong/issues/12079 if immediate upgrade is not possible.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-63037. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart