Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-63037: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache I

57
This month
CRITICAL 9.8REMOTEWATCHLISTUPGRADE

CVE-2026-63037 is a critical-severity flaw (CVSS 9.8) affecting inlong. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache InLong. This appears to allow SQL injection in the ORDER BY clause against the Manager backend database. This issue affects Apache InLong: from 2.0.0 before 2.4.0. Users are advised to upgrade to Apache InLong's 2.4.0 or cherry-pick [1] to solve it. [1]  https://github.com/apache/inlong/issues/12079 .

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.7% (top 48%)
CISA exploited listNo
WeaknessCWE-89
Published2026-08-20
Last modified2026-10-18
Publisher (CNA): Apache Software Foundation · Vendor: apache

Share: LinkedIn · X · Reddit

Last updated 2026-10-18 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

apache inlong UPGRADE
Affected: >= 2.0.0 and < 2.4.0
Fixed in: 2.4.0
Safe to downgrade to: a release before 2.0.0
1. Check installed version
apt-cache policy inlong || rpm -q inlong || inlong --version
2. UPGRADE to 2.4.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade inlong
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade inlong
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)
apt-cache madison inlong sudo apt install inlong=<VERSION_BEFORE_2.0.0> sudo apt-mark hold inlong
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list inlong sudo dnf downgrade inlong-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add inlong
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-63037?

inlong: upgrade to 2.4.0. Exact commands for each OS are on this page.

Is CVE-2026-63037 being exploited?

CVE-2026-63037 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-63037 affect?

CVE-2026-63037 affects inlong. Severity is critical (CVSS 9.8). Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache InLong. This appears to allow SQL injection in the ORDER BY clause against the Manager backend database. This issue affects Apache

How urgent is CVE-2026-63037?

Priority 57/100. Critical severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

GitHub vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.