CVE-2024-55160: GFast between v2 to v3.2 was discovered to contain a SQL injection vulnerability via the OrderBy parameter at

This week

CRITICAL 9.8REMOTEUPGRADE

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

GFast between v2 to v3.2 was discovered to contain a SQL injection vulnerability via the OrderBy parameter at /system/operLog/list.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 54%)
CISA exploited list	No
Weakness	CWE-89
Published	2025-02-27
Last modified	2026-07-05

Publisher (CNA): MITRE · Vendor: g-fast

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

Am I affected?

Timeline

2025-02-27 21:15 UTCPublished CVE record published
2026-07-05 01:21 UTCUpdated Record last modified

g-fast gfast UPGRADE

Affected: >= 2 and <= 3.2

Fixed in: newer than 3.2

Safe to downgrade to: a release before 2

1. Check installed version

apt-cache policy gfast || rpm -q gfast || gfast --version

2. UPGRADE to newer than 3.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade gfast

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade gfast

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 (Debian / Ubuntu)

apt-cache madison gfast sudo apt install gfast=<VERSION_BEFORE_2> sudo apt-mark hold gfast

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list gfast sudo dnf downgrade gfast-<VERSION_BEFORE_2> sudo dnf versionlock add gfast

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-2024-55160?

gfast: upgrade to newer than 3.2. Exact commands for each OS are on this page.

Is CVE-2024-55160 being exploited?

CVE-2024-55160 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-2024-55160 affect?

CVE-2024-55160 affects gfast. Severity is critical (CVSS 9.8). GFast between v2 to v3.2 was discovered to contain a SQL injection vulnerability via the OrderBy parameter at /system/operLog/list.

How urgent is CVE-2024-55160?

Priority 56/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs