CVE-2026-63039: Apache InLong · SQL Injection
Affects Apache InLongSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.4.0 as a priority.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.4.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade Apache InLong and org.apache.inlong/inlong-manager to 2.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache InLong | Affected
| Fixed in
|
Mavenorg.apache.inlong/inlong-managerpkg:maven/org.apache.inlong/inlong-managerOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users are advised to upgrade Apache InLong to version 2.4.0 or later. Alternatively, they can apply the patch available in the Apache InLong GitHub pull request #12080. No other mitigation or temporary workaround is indicated by the vendor advisory.
Description
CVE-2026-63039 is a critical SQL Injection vulnerability in Apache InLong versions from 2.0.0 up to but not including 2.4.0. This flaw allows attackers to inject malicious SQL commands by improperly neutralizing special elements in SQL statements. The vulnerability is fixed in Apache InLong version 2.4.0. Users should upgrade to version 2.4.0 or apply the relevant patch to remediate this issue.