Skip to main content
VulnerabilityPublished Updated

CVE-2026-63044: Apache InLong · Server-Side Request Forgery (SSRF)

Affects Apache InLongSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium : upgrade to 2.4.0 when convenient.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Apache InLong to 2.4.0.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache InLongAffected
  • >=2.0.0 <2.4.0
Fixed in
  • 2.4.0

AI-suggested

Users should upgrade Apache InLong to version 2.4.0 or later. Alternatively, they can apply the patch referenced in the Apache InLong GitHub pull request https://github.com/apache/inlong/pull/12130. No other mitigation or temporary workaround is indicated.

Description

CVE-2026-63044 is a Server-Side Request Forgery (SSRF) vulnerability in Apache InLong that allows any authenticated user, without requiring admin privileges, to make the InLong Manager server send outbound HTTP requests or TCP connections to arbitrary internal hosts and ports. This affects Apache InLong versions from 2.0.0 up to but not including 2.4.0. The issue is addressed in version 2.4.0 and can also be mitigated by applying the referenced patch from the Apache InLong GitHub repository.

References

Community reviews

Loading reviews…