Skip to main content
VulnerabilityPublished Updated

CVE-2026-63040: Apache InLong · Exposed Files or Directories

Affects Apache InLongSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 2.4.0 soon.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% 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:N/I:H/A:H

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 and org.apache.inlong/inlong-manager to 2.4.0.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache InLongAffected
  • >=2.0.0 <2.4.0
Fixed in
  • 2.4.0
Mavenorg.apache.inlong/inlong-managerpkg:maven/org.apache.inlong/inlong-managerOther threatsAffected
  • =2.0.0
  • >=2.0.0 <2.4.0
Fixed in
  • 2.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available by upgrading Apache InLong to version 2.4.0 or by applying the patch from the referenced pull request (https://github.com/apache/inlong/pull/12145). Users should promptly apply these updates to remediate the vulnerability.

Description

CVE-2026-63040 is a vulnerability in Apache InLong versions from 2.0.0 up to but not including 2.4.0. The issue arises because the StreamSource component does not perform authorization checks, allowing any authenticated user to logically delete all stream sources. This vulnerability has a high severity score of 8.1 and impacts integrity and availability without affecting confidentiality. Users are advised to upgrade to version 2.4.0 or apply the specific patch referenced in the vendor's pull request to remediate the issue.

References

Community reviews

Loading reviews…