Skip to main content
VulnerabilityPublished Updated

CVE-2026-63038: Apache InLong · SQL Injection

Affects Apache InLongSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.4.0 as a priority.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 53% 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:N/UI:N/S:U/C:H/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 16 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 GitHub issue https://github.com/apache/inlong/issues/12135. No other mitigation guidance is provided by the vendor advisory.

Description

CVE-2026-63038 is a critical SQL Injection vulnerability in Apache InLong affecting versions from 2.0.0 up to but not including 2.4.0. The flaw allows attackers to inject arbitrary SQL code via the dbName, tableName, schemaName, and username parameters. This can lead to full compromise of confidentiality, integrity, and availability of the affected system. Users are advised to upgrade to version 2.4.0 or apply the relevant patch to remediate the issue.

References

Community reviews

Loading reviews…