Quick answers
- Is CVE-2026-63046 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63046 being exploited in the wild.
- How severe is CVE-2026-63046?
- High severity, with a CVSS score of 8.8, published 21 August 2026.
- Which products and versions are affected?
- Apache Inlong 2.0.0 to 2.3.x.
- Is there a fix for CVE-2026-63046?
- A patch was published on 2026-08-21: Fix available in version 2.4.0 and via pull requests #12151 and #12155 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63046 attacked?
- It is attacked over the network or with local access, in a hosted service.
- Am I affected by CVE-2026-63046?
- 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 vulnerability is an argument injection flaw (CWE-88) in the ExcuteLinux.exeCmd() method of Apache InLong's Agent Installer ModuleManager, which constructs and executes shell commands without filtering or whitelist validation of user-supplied arguments. The vulnerable component directly interpolates user input into shell commands, enabling an attacker to break out of the intended command context and inject arbitrary shell metacharacters and commands. Network reachability and authentication status depend on how ModuleManager is exposed; typical exploitation requires local or adjacent network access to the installer component. A successful attack allows arbitrary command execution with the privileges of the InLong process. Patches are available in Apache InLong 2.4.0 and via cherry-picked commits in the project repository.
Affected products
- Apache InLong 2.0.0 to 2.3.x
Timeline
- 2026-08-21: disclosed
- 2026-08-21: patched: Fix available in version 2.4.0 and via pull requests #12151 and #12155