CVE-2026-63016: Apache InLong · Uncontrolled Resource Consumption
Affects Apache InLongSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.4.0 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% 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:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 20 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade Apache InLong to 2.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache InLong | Affected
| Fixed in
|
GitHubapache/inlongpkg:github/apache/inlongOther 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 should upgrade Apache InLong to version 2.4.0 or later. Alternatively, they can apply the patches referenced in the official GitHub pull requests (https://github.com/apache/inlong/pull/12095 and https://github.com/apache/inlong/pull/11732). Patch status is not explicitly confirmed in the advisory, but the vendor's upgrade recommendation indicates an official fix is available.
Description
Uncontrolled Resource Consumption vulnerability in Apache InLong. Users could affect operational configuration or allow upload of non-official packages. 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/pull/12095 https://github.com/apache/inlong/pull/11732