VulnerabilityPublished 29 Oct 2024Updated 15 Oct 2025

CVE-2024-7010: mudler/localai · Timing Side Channel

Affects mudler/localaiSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.0 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubmudler/localai`pkg:github/mudler/localai`Other threats	Affected =2.17.1	Fixed in–

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-2024-7010, European organizations should first verify if they are using mudler/localai version 2.17.1 or earlier and monitor vendor communications for patches. In the absence of an official patch, implement constant-time password comparison functions to eliminate timing discrepancies during authentication. This involves using cryptographic libraries designed to perform comparisons in fixed time regardless of input. Additionally, enforce strict rate limiting and account lockout policies to reduce the feasibility of iterative timing attacks. Deploy network-level protections such as Web Application Firewalls (WAFs) configured to detect and block suspicious authentication request patterns. Enable detailed logging and continuous monitoring of authentication attempts to identify anomalies indicative of timing attacks. Where possible, integrate multi-factor authentication (MFA) to reduce reliance on password secrecy alone. Conduct regular security assessments and penetration tests focusing on timing side-channel vulnerabilities. Finally, educate developers and security teams about side-channel risks and secure coding practices to prevent similar issues in future software versions.

Description

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.

Impact

For European organizations, the primary impact of CVE-2024-7010 is the compromise of confidentiality through unauthorized access to systems protected by mudler/localai authentication. Attackers can leverage timing discrepancies to deduce valid credentials without needing prior access or user interaction, increasing the risk of account takeover. This can lead to data breaches, unauthorized data access, and potential lateral movement within networks. Since integrity and availability are not directly affected, the immediate operational disruption may be limited; however, the breach of credentials can facilitate further attacks that impact these areas. Organizations in sectors such as finance, healthcare, government, and critical infrastructure that rely on mudler/localai for authentication are at heightened risk. The vulnerability's remote exploitability and low attack complexity make it attractive for attackers targeting European entities, especially those with high-value data or strategic importance. The absence of known exploits currently provides a window for proactive defense, but the risk of future exploitation remains significant. Failure to address this vulnerability could undermine trust in affected systems and lead to regulatory penalties under GDPR if personal data is compromised.

CWE-208Observable Timing Discrepancy (opens in a new tab)
Base weakness
Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Cross-Domain Search Timing (opens in a new tab)
Application Fingerprinting (opens in a new tab)
System Footprinting (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Oct 2025, 13:33 UTC

WeaknessesCWE-208

Technical details

References

Community reviews

Related threats