CVE-2026-63042: Apache InLong · Exposed Files or Directories
Affects Apache InLongSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 2.4.0 soon.
Data as of 16 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:L/UI:N/S:U/C:N/I:H/A:HExploitation 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 16 Nov 2026.
What to do
Upgrade Apache InLong and org.apache.inlong/inlong to 2.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache InLong | Affected
| Fixed in
|
Mavenorg.apache.inlong/inlongpkg:maven/org.apache.inlong/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 to remediate this vulnerability. Alternatively, they can cherry-pick the patch referenced in the Apache InLong GitHub pull request #12161. No other mitigation is indicated by the vendor advisory.
Description
CVE-2026-63042 is a vulnerability in Apache InLong versions from 2.0.0 up to but not including 2.4.0. It allows any authenticated user with access to the manager interface to create, modify, and delete Data Node definitions due to files or directories being accessible to external parties. This issue is addressed in Apache InLong version 2.4.0.