CVE-2024-7010: mudler/localai version 2.17.1 is vulnerable to a Timing Attack

This week

MEDIUM 5.9REMOTEDOWNGRADE

CVE-2024-7010 is a medium-severity flaw (CVSS 5.9) affecting localai. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

mudler/localai version 2.17.1 is vulnerable to a Timing Attack. This type of side-channel attack allows an attacker to compromise the cryptosystem by analyzing the time taken to execute cryptographic algorithms. Specifically, in the context of password handling, an attacker can determine valid login credentials based on the server's response time, potentially leading to unauthorized access.

Why this priority

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

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 56%)
CISA exploited list	No
Weakness	CWE-208, CWE-203
Published	2024-10-29
Last modified	2026-06-17

Publisher (CNA): huntr.dev · Vendor: mudler

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

Am I affected?

Timeline

2024-10-29 13:15 UTCPublished CVE record published
2026-06-17 08:19 UTCUpdated Record last modified

mudler localai DOWNGRADE

Affected: 2.17.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.17.1

1. Check installed version

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

2. No fixed release: DOWNGRADE to a release before 2.17.1 (Debian / Ubuntu)

apt-cache madison localai sudo apt install localai=<VERSION_BEFORE_2.17.1> sudo apt-mark hold localai

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list localai sudo dnf downgrade localai-<VERSION_BEFORE_2.17.1> sudo dnf versionlock add localai

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-7010?

localai: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-7010 being exploited?

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

CVE-2024-7010 affects localai. Severity is medium (CVSS 5.9). mudler/localai version 2.17.1 is vulnerable to a Timing Attack. This type of side-channel attack allows an attacker to compromise the cryptosystem by analyzing the time taken to execute cryptographic algorithms. Specifically, in the context

How urgent is CVE-2024-7010?

Priority 42/100. Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2024-9900 MEDIUM 6.1 DOWNGRADE mudler/localai version v2.21.1 contains a Cross-Site Scripting (XSS) vulnerability in its search functionality
CVE-2024-6983 HIGH 8.8 DOWNGRADE mudler/localai version 2.17.1 is vulnerable to remote code execution
CVE-2024-6868 CRITICAL 9.8 DOWNGRADE mudler/LocalAI version 2.17.1 allows for arbitrary file write due to improper handling of automatic archive ex
CVE-2024-6095 MEDIUM 5.8 UPGRADE A vulnerability in the /models/apply endpoint of mudler/localai versions 2.15.0 allows for Server-Side Request
CVE-2024-5616 MEDIUM 4.3 UPGRADE A Cross-Site Request Forgery (CSRF) vulnerability exists in mudler/LocalAI versions up to and including 2.15.0

References

← Back to latest CVEs