Skip to main content
VulnerabilityPublished Updated

CVE-2022-40955: Apache InLong · Deserialization of Untrusted Data

Affects Apache InLongSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 1.3.0 soon.

Data as of 26 Oct 2026, 09:08 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Sep 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade org.apache.inlong/inlong-manager to 1.3.0.

Affected software

ProductAffectedFixed in
Mavenorg.apache.inlong/inlong-managerpkg:maven/org.apache.inlong/inlong-managerOther threatsAffected
  • <1.3.0
Fixed in
  • 1.3.0

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

AI-suggested

To mitigate CVE-2022-40955, European organizations should: 1) Immediately upgrade Apache InLong to version 1.3.0 or later, where the vulnerability is patched. 2) Restrict and audit privileges related to database connection configurations, ensuring only trusted administrators have the ability to specify JDBC URL parameters and write data to the MySQL database. 3) Implement strict input validation and sanitization on data written to the database to prevent injection of malicious serialized objects. 4) Employ network segmentation and firewall rules to limit access to Apache InLong servers and associated databases, reducing the attack surface. 5) Monitor logs and database transactions for unusual activities indicative of exploitation attempts, such as unexpected serialized data or anomalous connection parameter changes. 6) Conduct regular security assessments and penetration testing focused on deserialization vulnerabilities and privilege escalation paths. 7) Consider deploying runtime application self-protection (RASP) or application-layer firewalls capable of detecting and blocking deserialization attacks. These targeted measures go beyond generic patching and help reduce the risk of exploitation in complex enterprise environments.

Description

In versions of Apache InLong prior to 1.3.0, an attacker with sufficient privileges to specify MySQL JDBC connection URL parameters and to write arbitrary data to the MySQL database, could cause this data to be deserialized by Apache InLong, potentially leading to Remote Code Execution on the Apache InLong server. Users are advised to upgrade to Apache InLong 1.3.0 or newer.

References

Community reviews

Loading reviews…