dbcve.org
LocalaiApplication · Mudler

CVE-2024-6095

MEDIUM · 5.8 CVSS v3.1 Published 2024-07-06
Fix available
A fix is available. Upgrade to 2.17.0 or later.
See remediation →
67/100
Remediation priority · Elevated
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability in the /models/apply endpoint of mudler/localai versions 2.15.0 allows for Server-Side Request Forgery (SSRF) and partial Local File Inclusion (LFI). The endpoint supports both http(s):// and file:// schemes, where the latter can lead to LFI. However, the output is limited due to the length of the error message. This vulnerability can be exploited by an attacker with network access to the LocalAI instance, potentially allowing unauthorized access to internal HTTP(s) servers and partial reading of local files. The issue is fixed in version 2.17.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-918

The server can be induced to make requests to a URL an attacker controls, turning it into a proxy into internal networks and cloud metadata services. It's especially dangerous behind a trusted network boundary. The fix is strict allow-listing of destinations and blocking access to internal address ranges.

General guidance for the server-side request forgery (ssrf) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LocalaiApplication
Affected:< 2.17.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.17.0 or later
Fixed in 2.17.0
Vendor patch github.com →
Recommended fix High confidence

LocalAI version 2.17.0 or later (e.g., v2.17.0, v2.17.1, latest stable)

  1. 1. Identify the currently running LocalAI version by checking the container/process or using `localai --version` or checking the Docker image tag
  2. 2. Plan the upgrade - schedule a maintenance window as the service may need a brief restart
  3. 3. Backup LocalAI configuration files, especially any custom YAML configs in /etc/localai or the data directory
  4. 4. Stop the LocalAI service or container
  5. 5. Upgrade LocalAI to version 2.17.0 or later. For Docker: `docker pull mudler/localai:v2.17.0` or update your docker-compose.yaml image tag. For binary: download the new release from the GitHub releases page
  6. 6. Restart the LocalAI service or container
  7. 7. Verify the upgrade was successful by checking the version again
  8. 8. Test the /models/apply endpoint to confirm the vulnerability is mitigated - ensure it no longer accepts file:// URLs and properly validates http(s):// URLs
Caveat Review release notes between your current version and 2.17.0 for any breaking changes to API endpoints or configuration format; minor version upgrades within 2.x typically maintain backward compatibility

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,850. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6095 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6095 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data