Quick answers
- Is CVE-2026-63015 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63015 being exploited in the wild.
- How severe is CVE-2026-63015?
- Medium severity, with a CVSS score of 4.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-63015?
- A patch was published on 2026-08-20: Version 2.4.0 released; patches available via GitHub PRs #12093 and #11732 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63015 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-63015?
- 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 authorization bypass / information disclosure flaw in Apache InLong's template access control mechanism. Non-authorized users (those without template owner/responsible person status) can view template metadata and configuration information that should be restricted. The vulnerability exists in versions 2.0.0 before 2.4.0 and is classified as uncontrolled resource consumption by the advisory, though the practical impact is information disclosure. A network-accessible attacker with user-level access to InLong can enumerate and view template details without proper entitlements. The fix is available in version 2.4.0 or via cherry-pick patches (PRs #12093 and #11732).
Affected products
- Apache InLong 2.0.0 to before 2.4.0
Timeline
- 2026-08-20: disclosed
- 2026-08-20: patched: Version 2.4.0 released; patches available via GitHub PRs #12093 and #11732