Inlong vulnerabilitiesRanked by how likely they are to be used.

Product21 versions
The short answer

Inlong is made by Apache. We track 31 published vulnerabilities in it, across 21 versions. None of them is on the list of flaws known to be exploited today. If you run Inlong, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Inlong vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Inlong's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Inlong flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 2.7%

    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...

    CVSS8.8Published20 Sep 2022
  2. 1.7%

    Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in Apache InLong.This issue affects Apache InLong: from 1.4.0 through 1.8.0, the attacker can create...

    CVSS7.5Published16 Oct 2023
  3. 1.7%

    Deserialization of Untrusted Data Vulnerability in Apache Software Foundation Apache InLong.This issue affects Apache InLong: from 1.4.0 through 1.7.0.

    CVSS7.5Published25 Jul 2023
  4. 1.6%

    Improper Neutralization of Special Elements Used in an SQL Command ('SQL Injection') vulnerability in Apache Software Foundation Apache InLong.This issue affects Apache InLong: from 1.4.0 through 1.7.0.

    CVSS9.8Published25 Jul 2023
  5. 1.6%

    Improper Control of Generation of Code ('Code Injection') vulnerability in Apache InLong.This issue affects Apache InLong: from 1.5.0 through 1.9.0, which could lead to Remote Code Execution.

    CVSS9.8Published3 Jan 2024
  6. 1.5%

    Deserialization of Untrusted Data vulnerability in Apache Software Foundation Apache InLong.

    CVSS8.8Published27 Mar 2023
  7. 1.4%

    Authorization Bypass Through User-Controlled Key vulnerability in Apache InLong.This issue affects Apache InLong: from 1.4.0 through 1.8.0, some sensitive params checks will be bypassed, like...

    CVSS9.8Published16 Oct 2023
  8. 1.4%

    Deserialization of Untrusted Data Vulnerability in Apache Software Foundation Apache InLong.

    CVSS7.5Published19 Oct 2023
  9. 1.4%

    Files or Directories Accessible to External Parties vulnerability in Apache Software Foundation Apache InLong.This issue affects Apache InLong: from 1.4.0 through 1.6.0.

    CVSS9.1Published22 May 2023
  10. 1.3%

    Deserialization of Untrusted Data vulnerability in Apache Software Foundation Apache InLong.This issue affects Apache InLong: from 1.1.0 through 1.5.0.

    CVSS9.8Published1 Feb 2023
EdgeProtect

Running Inlong? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 31 published vulnerabilities listed under the name Inlong, across 21 versions.

None of Inlong's vulnerabilities is on the list of flaws known to be exploited today.

Create a EdgeProtect account and track Inlong. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.