Skip to content
Fencer Intel
high 7.5

CVE-2024-5182 in the critical feed json

Path Traversal in mudler/localai

published 2y ago modified 4mo ago also GHSA-cpcx-r2gq-x893 , GO-2024-2938 , EUVD-2024-2025

cvss
7.5
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
25.5%
EPSS 25.5% chance of exploitation in 30 days, percentile 97%
public exploits
0
none known

Summary

A path traversal vulnerability exists in mudler/localai version 2.14.0, where an attacker can exploit the `model` parameter during the model deletion process to delete arbitrary files. Specifically, by crafting a request with a manipulated `model` parameter, an attacker can traverse the directory structure and target files outside of the intended directory, leading to the deletion of sensitive data. This vulnerability is due to insufficient input validation and sanitization of the `model` parameter.

Patch / fix

  • go github.com/go-skynet/LocalAI 2.16.0
  • mudler mudler/localai 2.16.0
  • mudler localai 2.16.0

Is CVE-2024-5182 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
2y ago

Exploit prediction

25.54% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • huntr.com https://huntr.com/bounties/f7a87f29-c22a-48e8-9fce-b6d5a273e545 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
GitHub 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/go-skynet/LocalAI
<2.16.0
all versions
2.16.0

Affected products

  • mudler mudler/localai
  • mudler localai

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.