Quick answers
- Is CVE-2026-63042 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63042 being exploited in the wild.
- How severe is CVE-2026-63042?
- High severity, with a CVSS score of 8.1, 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-63042?
- A patch was published on 2026: Fixed in Apache InLong 2.4.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63042 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-63042?
- 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
The vulnerability is a missing authorization check on DataNode management endpoints in Apache InLong. While authentication is required to access the manager, the application fails to properly verify that the authenticated user has the appropriate permissions to create, modify, or delete Data Node definitions. An authenticated attacker can directly interact with these endpoints to make unauthorized changes to data node configurations. The vulnerability affects versions 2.0.0 through 2.3.x, and is resolved in version 2.4.0 via the authorization control implementation referenced in the patch.
Affected products
- Apache InLong 2.0.0 to before 2.4.0
Timeline
- 2026-08-20: disclosed: CVE-2026-63042 published
- 2026: patched: Fixed in Apache InLong 2.4.0