Quick answers
- Is CVE-2026-63044 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63044 being exploited in the wild.
- How severe is CVE-2026-63044?
- Medium severity, with a CVSS score of 5.4, 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-63044?
- A patch was published on 2026-08-20: Fix available 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-63044 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-63044?
- 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 Server-Side Request Forgery (SSRF) flaw in the POST /api/node/testConnection endpoint of Apache InLong Manager. Any authenticated user without requiring administrative privileges can submit a crafted request to cause the server to initiate outbound connections to arbitrary internal or external hosts and ports. This allows attackers to probe internal network topology, interact with internal services, access metadata endpoints, or pivot to other systems. The vulnerability affects versions 2.0.0 through 2.3.x, and patches are available in version 2.4.0 or via the referenced pull request.
Affected products
- Apache InLong 2.0.0 to 2.3.x
Timeline
- 2026-08-20: disclosed: CVE-2026-63044 disclosed via oss-security mailing list
- 2026-08-20: patched: Fix available in Apache InLong 2.4.0