Quick answers
- Is CVE-2026-63039 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63039 being exploited in the wild.
- How severe is CVE-2026-63039?
- Critical severity, with a CVSS score of 9.8, published 20 August 2026.
- Which products and versions are affected?
- Apache Inlong from 2.0.0 before 2.4.0.
- Is there a fix for CVE-2026-63039?
- A patch was published on 2026-08-20: Fixed in Apache InLong 2.4.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63039 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-63039?
- 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
The vulnerability is a SQL injection (CWE-89) in the AuditAlertRuleService component, arising from improper neutralization of special elements in SQL commands via unvalidated MyBatis dollar-sign string interpolation. An attacker can inject arbitrary SQL by manipulating input values that are concatenated directly into SQL statements without proper parameterization or sanitization. The attack is network-accessible and does not require authentication or user interaction beyond crafting a malicious request. An attacker can execute arbitrary SQL queries with the database credentials of the application, potentially exfiltrating data, modifying records, or causing denial of service. The fix is available in Apache InLong version 2.4.0 or via a specific cherry-pick commit.
Affected products
- Apache InLong from 2.0.0 before 2.4.0
Timeline
- 2026-08-20: disclosed
- 2026-08-20: patched: Fixed in Apache InLong 2.4.0