Quick answers
- Is CVE-2026-63016 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63016 being exploited in the wild.
- How severe is CVE-2026-63016?
- Medium severity, with a CVSS score of 5.3, published 20 August 2026.
- Which products and versions are affected?
- Apache Inlong 2.0.0 to before 2.4.0.
- Is there a fix for CVE-2026-63016?
- A patch was published on 2026-08-20: Fixed 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-63016 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-63016?
- 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 uncontrolled resource consumption vulnerability in Apache InLong affecting versions 2.0.0 through 2.4.0. The root cause stems from insufficient validation of package uploads and configuration changes, allowing authenticated (ordinary) users to consume excessive resources or upload unauthorized packages. The attack requires network access to InLong and valid user credentials. An attacker can exploit this to disrupt service operations or inject non-official packages for code execution. Fixes are available in version 2.4.0 or via cherry-picking patches from the referenced GitHub pull requests.
Affected products
- Apache InLong 2.0.0 to before 2.4.0
Timeline
- 2026-08-20: disclosed
- 2026-08-20: patched: Fixed in version 2.4.0