# CVE-2024-5821: Local File Inclusion (LFI) in stitionai/devika

> Attackers can read sensitive server files by exploiting file name correction logic in the Devika AI agent.

- **Severity:** Medium 6.2 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2024
- **Updated:** 15 Oct 2025
- **Also known as:** GHSA-f8j4-pwp4-c58m

## What is CVE-2024-5821?

CVE-2024-5821 is a medium-severity path traversal vulnerability in stitionai/devika, published on 3 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The vulnerability allows an attacker to access sensitive files on the server by confusing the agent with incorrect file names. When a user requests the content of a file with a misspelled name, the agent attempts to correct the command and inadvertently reveals the content of the intended file, such as /etc/passwd. This can lead to unauthorized access to sensitive information and potential server compromise.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2024-5821?


## How do I fix CVE-2024-5821?

No fix has been published for CVE-2024-5821 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-5821 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-5821 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5821 and fix it if it is affected.

What it is: CVE-2024-5821 is a medium-severity path traversal vulnerability in stitionai/devika, published on 3 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-5821 exists.

Affected product: stitionai/devika. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-5821/ (Markdown: https://insights.sbomify.com/CVE-2024-5821/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-5821
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-5821
- OSV: https://osv.dev/vulnerability/CVE-2024-5821

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-5821/
Summaries are generated and may contain mistakes; the official description above is the record.