Quick answers
- Is CVE-2026-63043 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63043 being exploited in the wild.
- How severe is CVE-2026-63043?
- High severity, with a CVSS score of 7.5, published 20 August 2026.
- Which products and versions are affected?
- Apache Inlong 2.0.0 to 2.3.x.
- Is there a fix for CVE-2026-63043?
- A patch was published on 2026-08-20: Fix available 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-63043 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-63043?
- 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
A relative path traversal vulnerability exists in Apache InLong's Agent component due to insufficient validation of file source paths. An attacker can craft malicious input using path traversal sequences (e.g., ../) to escape the intended directory and read arbitrary files from the Agent host filesystem. The vulnerability affects versions 2.0.0 through 2.3.x; exploitation requires network access to the Agent. The vulnerability has been patched in version 2.4.0, and users are advised to upgrade or apply the fix from https://github.com/apache/inlong/pull/12146.
Affected products
- Apache InLong 2.0.0 to 2.3.x
Timeline
- 2026-08-20: disclosed
- 2026-08-20: patched: Fix available in version 2.4.0