# CVE-2024-6825: Remote Code Execution in BerriAI/litellm

> Attackers can execute arbitrary code by injecting malicious callbacks into the post_call_rules configuration in LiteLLM.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2025
- **Updated:** 15 Oct 2025
- **Also known as:** GHSA-53gh-p8jc-7rg8, PYSEC-2026-1541

## What is CVE-2024-6825?

CVE-2024-6825 is a high-severity code injection vulnerability in berriai/litellm, published on 20 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

BerriAI/litellm version 1.40.12 contains a vulnerability that allows remote code execution. The issue exists in the handling of the 'post_call_rules' configuration, where a callback function can be added. The provided value is split at the final '.' mark, with the last part considered the function name and the remaining part appended with the '.py' extension and imported. This allows an attacker to set a system method, such as 'os.system', as a callback, enabling the execution of arbitrary commands when a chat response is processed.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

3 open source packages ship an affected version, including litellm. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `litellm` | PyPI | From 1.40.3.dev2 to 1.40.12 | None |
| `litellm` | PyPI | From 1.40.3.dev2 to 1.40.12 | None |
| `litellm` | PyPI | From 1.40.3.dev2 to 1.40.12 | None |

Products: Litellm Litellm.

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

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

## Is CVE-2024-6825 being exploited?

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

## Other vulnerabilities in berriai/litellm

- [CVE-2026-42208](https://insights.sbomify.com/CVE-2026-42208/): BerriAI LiteLLM SQL Injection (critical 9.3, exploited in the wild)
- [CVE-2026-59822](https://insights.sbomify.com/CVE-2026-59822/): BerriAI LiteLLM Improper Authentication (high 8.8, exploited in the wild)
- [CVE-2026-42271](https://insights.sbomify.com/CVE-2026-42271/): BerriAI LiteLLM Command Injection (high 8.7, exploited in the wild)
- [CVE-2024-5751](https://insights.sbomify.com/CVE-2024-5751/): Remote Code Execution in BerriAI/litellm (critical 9.8)
- [CVE-2024-2952](https://insights.sbomify.com/CVE-2024-2952/): Server-Side Template Injection in BerriAI/litellm (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6825 is a high-severity code injection vulnerability in berriai/litellm, published on 20 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6825 exists.

Affected packages and fixed versions:
- litellm (PyPI): affected from 1.40.3.dev2 up to 1.40.12; no fix listed
- litellm (PyPI): affected from 1.40.3.dev2 up to 1.40.12; no fix listed
- litellm (PyPI): affected from 1.40.3.dev2 up to 1.40.12; no fix listed

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-6825/ (Markdown: https://insights.sbomify.com/CVE-2024-6825/index.md)
```

## Sources

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

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