Quick answers
- Is CVE-2026-63037 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63037 being exploited in the wild.
- How severe is CVE-2026-63037?
- 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 2.3.x.
- Is there a fix for CVE-2026-63037?
- A patch was published on 2026-08-20: Fix available in version 2.4.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63037 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-63037?
- 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 an SQL injection vulnerability (CWE-89) in the ORDER BY clause of the Manager backend API endpoint for listing audit alert rules. The vulnerability is unauthenticated, meaning no credentials are required to exploit it. An attacker can inject specially crafted SQL through the affected endpoint to manipulate database queries, potentially exfiltrating sensitive data or modifying database records. The vulnerability affects Apache InLong versions 2.0.0 through 2.3.x, and is fixed in version 2.4.0 or via the commit referenced in the advisory.
Affected products
- Apache InLong 2.0.0 to 2.3.x
Timeline
- 2026-08-20: disclosed
- 2026-08-20: patched: Fix available in version 2.4.0